News for hackers. Stuff that matters.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by pjmlp on Tuesday October 15, 2019 @05:13AM (#21256782)
32G?!? Where does one find such employers???

Not to mention how crazy it sounds having 32GB for an IDE.

Visual Studio, Netbeans and Eclipse run perfectly fine with 8 GB.

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by simonh on Tuesday October 15, 2019 @05:34AM (#21256877)
I had a 32GB dev machine in my last job at a bank. 8GB is barely enough to run a full-on IDE, but if you also need to run wireshark, Geneos, outlook, big-ass excell sheets, several browsers with over a dozen tabs each, a bunch of communications tools, other office apps etc, etc, I'd regularly go above 20GB memory usage.

I was working app support really, with a fair bit of dev work as well, so needed to run a ton of different tools.

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by avgDev on Tuesday October 15, 2019 @03:38PM (#21262774)
I'm not even at a tech company and requested 32GBs, as I sometimes have VS and Android Studio open, running mobile emulators and checking what is going on the API end. You add VMs to the mix and one really needs 32GBs. My company had no issues providing the ram. Plus, it is insanely cheap right now.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by lultimouomo on Tuesday October 15, 2019 @05:55AM (#21256981)
I am self employed, and invested the lump sum of 800€ (+ screen that I already head) for a reasonably beefy desktop machine. I'm not saying that 32G is the minimum required to run JetBrains IDEs well; I'm saying 8G is not enough and 32G is definitely enough to run it alongside a bunch of containers and other stuff.

I agree that JetBrains stuff is resource hungry (maybe excessively so); to me it is still worth using it for Java, C#, Python, iOS and Android. For C++ I prefer Qt Creator (though I must say that the idea of switching to CLion and having a consistent IDE experience across all platforms that I work on is tempting).

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by jmkni on Tuesday October 15, 2019 @05:32AM (#21256865)
In my current role, I was given a laptop with 8GB. An additional 24GB mysteriously found it's way in there after a couple of days...
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by MrGilbert on Tuesday October 15, 2019 @05:35AM (#21256884)
It depends on your use-case.

Add Docker, VM, development database server etc. to the bill, and a 32 GB machine is pretty reasonable for a dev.

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by stoobs on Tuesday October 15, 2019 @10:00AM (#21258398)
All the Dev machines where I work have been 16GB for years, I wouldn't be surprised if we jumped to 32GB in the next hardware refresh.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by rafaelvasco on Tuesday October 15, 2019 @09:14AM (#21257985)
These days 32G is starting to become more of a necessity as apps take more and more RAM. And if you're a gaming, 8G doesn't cut it anymore for some games;