4 ms·

At the risk of starting a language flame-war: if I were starting a new company or effort, my default choice would be .NET Core. Performance is generally great

At the risk of starting a language flame-war: if I were starting a new company or effort, my default choice would be .NET Core. Performance is generally great and if you need to, there are lots of features in the language to allow you to further squeeze performance. C# is easy to pick up and has best-of-breed IDE support- you will get productive quickly. Also, you have an extremely large standard library at your disposal that is supported and dogfooded by Microsoft. Which is great because generally you do not need to install third party packages, but if you do NuGet is really easy to use. Edit: Forgot to mention the stellar documentation provided by Microsoft.

jaywalk 6y ago
FYI it's simply called .NET now, as of the release of .NET 5. Which is the successor to .NET Core 3.1.
- bob1029 6y ago
  With the existing volume of .NET Framework applications floating around, many of us find the need to be more precise in the specific framework we are talking about. Our shop still has a few tools that we haven't ported over yet.
intrasight 6y ago
Not a new company but rebooting an existing and am using .net. Being able to run on Google Cloud Run is awesome.
deleted 6y ago
[deleted]
bob1029 6y ago
The documentation is the best feature of the entire platform. If Microsoft hadn't published that deep-dive document regarding Blazor hosting models [1], I probably would have not given the technology a deeper look. But, after reading through and comparing the pros/cons of server-side vs client-side, it made it very clear to me that this was an approach that would be a really good fit for us (we went with the server-side model). My 2nd favorite feature is Self-Contained Deployments [2]. We skipped the whole containerization party because this approach completely obviated our need for such things. Beyond that, being able to seamlessly transition between imperative & functional members within the same type, pattern matching in switch statements [3], on-going awesomeness of LINQ, etc. Really great stuff to work with. [1] https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-5.0 https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-... [2] https://docs.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained https://docs.microsoft.com/en-us/dotnet/core/deploying/#publ... [3] https://docs.microsoft.com/en-us/dotnet/csharp/pattern-matching#when-clauses-in-case-expressions https://docs.microsoft.com/en-us/dotnet/csharp/pattern-match...

jaywalk 6y ago

FYI it's simply called .NET now, as of the release of .NET 5. Which is the successor to .NET Core 3.1.

bob1029 6y ago
With the existing volume of .NET Framework applications floating around, many of us find the need to be more precise in the specific framework we are talking about. Our shop still has a few tools that we haven't ported over yet.

intrasight 6y ago

Not a new company but rebooting an existing and am using .net. Being able to run on Google Cloud Run is awesome.

deleted 6y ago

[deleted]

bob1029 6y ago

The documentation is the best feature of the entire platform. If Microsoft hadn't published that deep-dive document regarding Blazor hosting models [1], I probably would have not given the technology a deeper look. But, after reading through and comparing the pros/cons of server-side vs client-side, it made it very clear to me that this was an approach that would be a really good fit for us (we went with the server-side model). My 2nd favorite feature is Self-Contained Deployments [2]. We skipped the whole containerization party because this approach completely obviated our need for such things. Beyond that, being able to seamlessly transition between imperative & functional members within the same type, pattern matching in switch statements [3], on-going awesomeness of LINQ, etc. Really great stuff to work with. [1] https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-5.0 https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-... [2] https://docs.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained https://docs.microsoft.com/en-us/dotnet/core/deploying/#publ... [3] https://docs.microsoft.com/en-us/dotnet/csharp/pattern-matching#when-clauses-in-case-expressions https://docs.microsoft.com/en-us/dotnet/csharp/pattern-match...