3 ms·
I've seen a disturbing amount of rhetoric from people at Microsoft who work on dotnet that aligns with this article. I'm not sure they have a good handle on how
by thrower123 5y ago
I've seen a disturbing amount of rhetoric from people at Microsoft who work on dotnet that aligns with this article. I'm not sure they have a good handle on how much enterprise code is still being written daily in "old dotnet", or if they do, they don't care. But the general sense is that legacy is lame, get with the cool kids on latest. Also we're encouraging OSS to drop support for you if you're on legacy, and we don't have a great upgrade path for you. Shades of the Great Python Split.
I don't really view the new dotnet core/5/6 platform as very stable, not when they are still releasing this often and making breaking changes.
- oaiey 5y agoThey release in the same cadence roughly. The difference is they are no longer grindlocked in Windows, VS and bad patterns. Result: less cloud costs by better performance, capability to run on Linux, lambdas, containers and ability to stay fresh and not turn into Cobol. I understand where you are. I also have to explain my manager ongoing costs for upgrades. Not only for .NET bit every part of the stack. Luckily we have cyber security as an ongoing excuse.