1,352 karma · joined November 22, 2017
.NET Framework (v1.0-4.8) - 4.8 Currently still supported, but don't build anything new in it. It only gets very minor updates. Not cross platform (Mono can help, but euuughhh), slower, stuck with C# 7.3.
.NET Core (v1.0-3.1) - Out of support, transition period between .NET Framework and modern .NET. Cross platform support, some support for AOT compile.
.NET (v6-8) - LTS every other version starting with 6, 36 months LTS, cross platform, magnitudes faster than .NET Framework. Successor to Framework and Core. Many features of .NET Framework have been abstracted to NuGet packages.
.NET Standard (v1.0-2.1) - Interop API specification for Framework/Core/.NET. Write a class library that targets .NET Standard and you can use it in more than one runtime. You'll see a lot of NuGet packages target Standard. If you're writing a class library you should probably target Standard.
"Core" products/packages - Many packages/libraries have been renamed to include "Core" in the title. ASP.NET Core, Entity Framework Core, etc. These are libraries/packages that only have implement their core functionality. For example, ASP.NET Core has some basic implementations, but does not include things like Web API, MVC, Authorization, Razor. If you build an ASP.NET Core project you'll be pulling in a lot of packages based on your needs. The features/libraries are more atomic and less reliant on a full version update of ASP.NET Core.
So yes, based on this experience it really sucks. That's what you get for the cheapest obsolete tech. It'd be great if people realized there's better electric appliances out there.
It's infuriating how many times I've run into games where the potential commands/switches have been documented online across 30 websites, but every site is incomplete. Tons of games don't even document how to set the listen address or port, or even what runtimes might be needed in order to run.
I don't know. I think it's silly for decades-old-games to run into licensing issues when trying to go open source. The tech is effectively obsolete except in the instance of that specific game.
I honestly would challenge you to find games from the mid 90's+ that won't work on a modern machine. Many times if there's a feature that straight up doesn't work it's due to online services being discontinued. There's been some work done to rebuild services like GameSpy or Westwood Online, but once more forms of encryption and anti-cheat or DRM were implemented in these sorts of services, the harder it's going to be to preserve their experience.
Yes, this will change over time. Unless there's a compatibility layer that's perfect though, I don't see this whole "x86 will be dead in 5 years" argument. That's what they said almost 15 years ago.
* When I say decent, I mean this absolutely should be the bare minimum, but this type of thing feels rare in the industry.