4 ms·

This kind of project is what could make me use C# instead of Go for my server needs Microsoft is sitting on a gold mine and they don't know it!! yet!

bob1029 5y ago
I have a feeling that Microsoft is abundantly aware of the value proposition of the new .NET ecosystem. C# has always been a good systems programming language. NET Core/5/6+ have just taken that to a new dimension with x-platform and better tooling. The best thing about the MS stack is that it is built for the 8000lb gorilla projects (I.e. their own internal stuff). If you have a unicorn solution that has 2000 projects and requires 36 hours to build, visual studio, msbuild (dotnet build) are the things you want to be relying on to get you through the day.
- pjc50 5y ago
  Msbuild will definitely cope with that. Visual Studio, for all that it's a great IDE, gets creaky around 50 projects, I cannot imagine how long it takes to load 2000 of the things.
  - eyegor 5y ago
    VS2015 was the last sturdy release. With VS2017 I had occasional hangs and crashes, but VS2019 either crashes or needs to be rebooted a couple times per day just to function. Intellicode is constantly breaking, test explorer only works reliability once a month, and it corrupts itself badly enough to need manual obj/ deletion at least once every few weeks. In their infinite wisdom, msbuild devs decided not to always clean the obj/ directory in the clean target by default. This is my experience on solutions with around a dozen projects, maybe 500k-1m loc across the solution. And it still barely understands how to use ram. Even if you let it see 64+gb, it will swap to disk.
    - Shadonototro 5y ago
      visual studio became slow and laggy (interface) the day they ported their UI to C#, then it went downhill and i moved to sublime text, i still have to use VS, only for the debugger

4 ms·

This kind of project is what could make me use C# instead of Go for my server needs Microsoft is sitting on a gold mine and they don't know it!! yet!

by Shadonototro 5y ago

bob1029 5y ago
I have a feeling that Microsoft is abundantly aware of the value proposition of the new .NET ecosystem. C# has always been a good systems programming language. NET Core/5/6+ have just taken that to a new dimension with x-platform and better tooling. The best thing about the MS stack is that it is built for the 8000lb gorilla projects (I.e. their own internal stuff). If you have a unicorn solution that has 2000 projects and requires 36 hours to build, visual studio, msbuild (dotnet build) are the things you want to be relying on to get you through the day.
- pjc50 5y ago
  Msbuild will definitely cope with that. Visual Studio, for all that it's a great IDE, gets creaky around 50 projects, I cannot imagine how long it takes to load 2000 of the things.
  - eyegor 5y ago
    VS2015 was the last sturdy release. With VS2017 I had occasional hangs and crashes, but VS2019 either crashes or needs to be rebooted a couple times per day just to function. Intellicode is constantly breaking, test explorer only works reliability once a month, and it corrupts itself badly enough to need manual obj/ deletion at least once every few weeks. In their infinite wisdom, msbuild devs decided not to always clean the obj/ directory in the clean target by default. This is my experience on solutions with around a dozen projects, maybe 500k-1m loc across the solution. And it still barely understands how to use ram. Even if you let it see 64+gb, it will swap to disk.
    - Shadonototro 5y ago
      visual studio became slow and laggy (interface) the day they ported their UI to C#, then it went downhill and i moved to sublime text, i still have to use VS, only for the debugger