3 ms·
> I would encourage using regular .Net, not .Net Core until they've reached a certain threshold This is terrible advice. .NET Framework has so many gotchas in
by Hawxy 5y ago
> I would encourage using regular .Net, not .Net Core until they've reached a certain threshold
This is terrible advice. .NET Framework has so many gotchas in its dependency management and binding redirect hell, not to mention ASP.NET 4.x is full of hidden "magic" and serious usability problems.
Anyone starting a new project should be on .NET 5/Core, and that's been true since the Core 2.x releases. Also, the generic hosting model[0] is a productivity game changer and gives you a complete batteries-included experience no matter the project type.
[0] https://docs.microsoft.com/en-us/dotnet/core/extensions/generic-host https://docs.microsoft.com/en-us/dotnet/core/extensions/gene...
- valdiorn 5y agowoah, I was a pretty expert C#/.NET developer until about 5 years ago, when I switched to Python and C++ for my dayjob. I've not kept up with the ecosystem since then. .NET Core was sort of in its infancy, and we were debating moving over at the point when I left that company, so I've never used Core. but ...I can barely read that page and understand what's going on! This is something I did notice with the c# codebases I worked on; you could date them to the month based on whatever "hot shit" patterns were used by each project. I thought this was normal for every language, but since working on large codebases in other languages, I've found that it's mostly a C# thing (Java has a bit of that too). But man, it's insane how much the language and the ecosystem has changed in 5 years.