4 ms·

There is nothing "lock-in" about .NET Core/.NET 5+. In fact, as you can see from this whole Hot Reload kerfuffle, even Microsoft themselves doesn't always like

There is nothing "lock-in" about .NET Core/.NET 5+. In fact, as you can see from this whole Hot Reload kerfuffle, even Microsoft themselves doesn't always like the spirit of open source present on their own .NET team! .NET Framework is another story, and was (and still is) tightly coupled to Windows. It's the entire reason .NET Core was started as a separate open source effort. Honestly, we're lucky .NET Core was even allowed to live as long as it has. Now, it's philanthropic culture is directly butting heads with the profit-oriented culture of the Visual Studio team.

quadrifoliate 5y ago
That's the thing – I don't understand why people will chain themselves to caring about all this when you acknowledge that “Microsoft themselves doesn't always like the spirit of open source present on their own .NET team!” Does .NET have some breakthrough features or support that other languages don't have? Are job opportunities better than, say, Java? I'm not understanding the upside here of following the Microsoft version of Keeping Up with the Kardashians.