4 ms·
Aye it’s a burning trash heap of everything thrown on top now. MSFT stacks are an ever ending wild ride of change, deprecation, constant direction shifting and
by m0xte 7y ago
Aye it’s a burning trash heap of everything thrown on top now.
MSFT stacks are an ever ending wild ride of change, deprecation, constant direction shifting and bugs.
I’ve been writing c# since 2002 and I’m quite frankly done now. It doesn’t help me solve problems now. It just creates new ones I don’t want to solve or have to pay to solve.
The IDE is buggy, the platform is buggy and the churn is so bad it’s a ridiculous prospect trying to build a non trivial business on it now.
Most companies are still stuck on classic .net because hardly anything is really portable to core. On top of that when you do finally drag it to core 2.2 then it’s deprecated so you have to rewrite half your MVC stack for 3.0.
And then there’s the customer abuse like opt out Telemetry.
- scarface74 7y agoHave you looked at the Javascript and front end ecosystem over the past 10 years? .Net is remarkably stable comparatively.
- m0xte 7y agoYeah I’ve avoided it intentionally!
- philliphaydon 7y agoDisagreed. Upgrading from 2.2 to 3.0/3.1 is not rewrite half your stack. I literally just upgraded a 1.5yo project at work from 2.2 to 3.1 in a couple of hours. I had 1 undocumented issue which took the bulk of the time to fix. Everything else was pretty much namespace fixes or EF being more explicit. 2.2 to 3.1 is probably the easiest upgrade I’ve ever done. You wanna talk about mvc 1 to 2/3, now that was a painful upgrade.
- yread 7y ago2.1 to 2.2 can be a bit of a pain though