Re:Making life easier for newcomers to the .NET ecosystem
by jmnicolas on Monday November 15, 2021 @04:09PM
(#29232790)
> There are shops where legacy .NET Framework 4.x solutions are being spun up today for no reason other than ignorance has taken hold.
I wish! 2 years ago we visited one of our providers and I soon discovered their solution was being actively developed on .net 3.5 and Visual Studio 2008.
To this day I still have to install .net 3.5 on our machines that use their software (.net 3.5 isn't installed by default on Windows 10) so I know for a fact they didn't upgrade.
Re:Making life easier for newcomers to the .NET ecosystem
by torginus on Monday November 15, 2021 @02:38PM
(#29231673)
That's understandable - I've just very recently had the 'privilege' of fixing something in a .net 4.5 project - everything, from the tooling, the testing, the baroque xml project format felt super complex, Visual Studio-centric and a huge downgrade from what I'm used to nowadays.
Re:Making life easier for newcomers to the .NET ecosystem
by ethbr0 on Monday November 15, 2021 @02:42PM
(#29231713)
Microsoft has a bizarre habit of overcomplicating every@&$1ing thing in their ecosystems.
I think because most of the features come out of customer request >> architecture plans.
As a result, you end up with a billion different weird behind-the-scene links and requirements that didn't have to be that way and consume unnecessary cognitive load when working with it.
Re:Making life easier for newcomers to the .NET ecosystem
by the_only_law on Wednesday November 17, 2021 @12:59PM
(#29256449)
> There are shops where legacy .NET Framework 4.x solutions are being spun up today for no reason other than ignorance has taken hold.
I’ve just about mentally broken down, unable to use the pattern matching features, among other features.
I feel like 99% of this is the historical perspective. If you dropped a totally new developer into a pure .NET 6 codebase w/ VS2022, I strongly suspect they would have a reasonable time of it.
IMO, senior developers who stopped following tech news are the primary reason the community has to struggle with this perception today. There are shops where legacy .NET Framework 4.x solutions are being spun up today for no reason other than ignorance has taken hold.
Arguably, the marketing disaster is still primarily Microsoft's fault, but I feel the community could do better with listening and adapting too.