3 ms·
Not sure why this is so aggressively downvoted. I work in legacy software and it's true. A firm that's still on .NET Framework, PHP 5.6, or Java 8 is likely to
by Capricorn2481 2y ago
Not sure why this is so aggressively downvoted. I work in legacy software and it's true. A firm that's still on .NET Framework, PHP 5.6, or Java 8 is likely to stay on those versions for the near future.
- BuckRogers 2y agoWe just moved from 4.6.1 to 4.8 this year. We maintain a frontend(++) for a major enterprise software package, and follow them. They just moved to 4.8 so we did as well. Not even the point release. The contractor I work for is pretty conservative, he likes his 1+ million dollar home and worldwide vacations. He won't be changing anything without being forced by Microsoft. Even if Microsoft puts in a huge effort to updating a migration tool to be seamless, we wouldn't use it. It'll only happen when either the larger enterprise corporation migrates, or when Microsoft forces people off 4.8.
- mattmanser 2y agoWriting C# code in modern .net is so much better. It's close to the change when get/settwrs were made mostly redunant (but not quite). Just so much less boiler plate that you didn't even really realize you were writing.
- croes 2y agoNothing bad on staying a still supported framework. Most of the time boring old technology beats shiny new one.