The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Having different meanings for the same word in different industries is one thing...
I've heard IT terms used differently in different IT companies.
Like there was this company where they used the term "front-end" for everything from code running in the browser to the IIS service that served the pages.
The back-end, for them, was everything that did not serve HTML pages.
To me, and other places I've worked, the front-end is just what's running in your browser, everything else is back-end.
Some people also use the term back-end to mean their database, while others don't include it and mention a database explicitly.
And those are just two words.
It's all just very confusing...
I thought it might be interesting to write a bit about System.Numerics.Vector (and probably System.Runtime.Intrinsics), which is one of those things that can be helpful (I still don't exactly like the Vector<T> API, but it can be used for some things and for other things I can throw in some System.Runtime.Intrinsics), but used more rarely than it deserves. It's not easy to get into.
Of course I can cover the usual suspects such as linear algebra and Fourier transforms, but it would be more interesting to have some examples that are less on the "pure math" side and more on the "just random stuff that comes up in programs" side.
Good candidates look like a loop over one or more arrays, nested loops and some "mild conditionals" and "innocent function calls" (Math.Max and such) are fine, but if it's a big rat's nest of control flow I probably can't use it.
None of it is commonly used. System.Numerics.Vector is the old API, and still barely used, mostly ignored. System.Runtime.Intrinsics is new and better but so new that it only exists in Core 3.0 previews.
I've had my i7 laptop with 8GB for at least 4 years now (started out on win 8.1).
It has worked fine. I could run
1. web browser
2. Android Studio
3. Android emulator
All at the same time and I never had a problem. Now, I cannot run those 3 or all my RAM is gone.
I can now only (barely) run the
1. web browser
2. android studio
The only way i can use my computer for Android development now is to use an externally connected android device to run/debug apps on. Very sad. This laptop is not able to upgrade to 16GB. I know. It's crazy and cheapo.
Actually, I can barely run the web browser when Android Studio is running. Not great.
When I open too many tabs the tabs just crash and burn.
Win 10 Ram Eater?
Anyways, I also noticed this in win 10 at work and now at home. Check out how many svchost.exe processes are running:
I just started Visual Studio 2019 on my machine to see what it would look like.
Loaded up a basic sized MVC project and it's at 300MB. Quite a difference compared to Android STudio and it's desire for 2GB of ram (AS @ 1.0GB and the two Java procs at 1 GB).
Check out how many svchost.exe processes are running:
I can't even fit them all on one screen (in task manager) see the snapshot : https://i.stack.imgur.com/bPaaD.png[^]
What is going on? Has anyone else noticed this?
The old Windows security model was severely lacking... but process isolation is actually quite good. The reason browsers consume so much RAM is because they are also taking advantage of process isolation and job object isolation. The operating system is now also taking advantage of process isolation.
Plus... in the old service model when a service crashed a half-dozen other services crashed along with it. You can go back to the old behavior by changing a registry key but you will not gain much by doing that.
For a development box I'd recommend a minimum of 16GB RAM.
That’s great information and very good points about what is happening.
And, you are, of course, correct, 16GB for development is a lot more realistic.
I just got away with it for so long I’ve gotten soft.