News for hackers. Stuff that matters.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by kgwxd on Tuesday March 21, 2023 @06:57PM (#35253923)
It's just .NET going forward (for now) if you don't need to worry about any old stuff.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by Kwpolska on Tuesday March 21, 2023 @07:25PM (#35254253)
The issue is with Googling (or Binging if you’re so inclined). If you google ".NET foobar", you might get answers for .NET Core, but you might also get old answers for the .NET Framework, written at a time when there was just one .NET, or when .NET Core was not as relevant and not the “real” .NET. Of course, it’s not super important if “foobar” is something simple and generic, like “.NET split string”, but when you get into the murky and obscure stuff, it might be hard to figure out if you’re reading an article about .NET Framework or .NET the-artist-formerly-known-as-Core.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by osigurdson on Tuesday March 21, 2023 @08:36PM (#35255014)
Suggest using ChatGPT instead of google.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by Kwpolska on Wednesday March 22, 2023 @07:33AM (#35259501)
Then go ahead and ask it, and tell us the results. A good query would be “How are assemblies loaded in .NET?”, and if the response talks about the Global Assembly Cache (GAC), app.config, or assembly redirections, it’s not applicable to the modern .NET.

I’m skeptical, ChatGPT is not magic, and it was trained on ~15 years’ worth of “there is only one .NET Framework, so we might as well call it .NET” content, ~5 years of “.NET Framework is for serious business, and there’s the cross-platform (mostly-)web .NET Core” content, and 1 year of “.NET 5 is the future of .NET”.