3 ms·
Unless you use server-side rendering or JS-only dependency, in which case you do need Node.js, its usage cannot be justified as it is a massive downgrade in eve
by neonsunset 3y ago
Unless you use server-side rendering or JS-only dependency, in which case you do need Node.js, its usage cannot be justified as it is a massive downgrade in every way vs .NET (ASP.NET Core + EF Core/Dapper combo).
Examples of major considerations are security vulnerabilities and dependency hell (both solved long ago in .NET), performance and memory footprint (the average expected difference in application code performance is >10x), and ability to reach performance ceiling with additional optimization, supported deployment targets, the quality of the languages themselves (C# and F#), interop with C/C++/Rust, IDE support, static typing, quality of the libraries in the ecosystem (fewer but much better), etc.
- _hao 3y agoA lot of people still have a negative opinion on .NET and C# where in fact it's probably the most productive combo and bang for your buck ever made when it comes to the quality of the actual framework, capabilities of the C# language (and to extent the other CLR languages like F#) and tooling. It checks all three boxes. There have been massive improvements in both support and new features after .NET Core came into being. Some people even say that they've been adding too much too fast recently. I don't know how it compares to Java and Go which seem to be the main competitors in that niche (not taking JS/Python/Ruby/PHP etc. into account), but I'd probably pick Go rather than Java myself if I had to abandon C#.