News for hackers. Stuff that matters.
Re:.NET Core, .NET 5; the Exodus of .NET Framework? by stefan_ on Thursday January 09, 2020 @04:02PM (#22005699)
The author seems to make a rather classic mistake; once told, I'm sure you'll recognize it in some of your current and past coworkers: they become intimately involved and emotionally invested in the evolution of their chosen toolkit.

In C++, which has a large community with this particular affliction, this usually means their code stops compiling with anything but a HEAD clang targeting C++20 and becomes utterly unrecognizable. In C#, following this post, a few framework gimmicks will apparently not be implemented in the old .NET: all code must utilize them or risk "exodus".

Java had a good immunization protocol: don't change the language for 10 years. All those people moved to Scala.

Meanwhile, of course, the real world continues to run just fine with ancient software written in ancient languages compiled with ancient tooling, targeting ancient operating systems. Your router is on Linux 2.6. Hell, you can start a new application targeting .NET Framework 4 today and Microsoft will keep that stuff running for another 20 years on Windows.

Re:.NET Core, .NET 5; the Exodus of .NET Framework? by lern_too_spel on Thursday January 09, 2020 @11:07PM (#22008233)
No, the problem is that their dependencies will use the new gimmicks, and if they need feature or security updates in those dependencies, they will need to migrate their applications to the new platform.
Re:.NET Core, .NET 5; the Exodus of .NET Framework? by tonyedgecombe on Friday January 10, 2020 @02:36AM (#22009123)
This is the problem with open source dependencies, they often don't have the financial pressures nor resources to maintain what the users need.
Re:.NET Core, .NET 5; the Exodus of .NET Framework? by Nuzzerino on Friday January 10, 2020 @09:35AM (#22011159)
Not sure why the downvotes, as this has been my experience numerous times, particularly in the Node.JS world.