🤷 This didn’t point out anything that’s not a technical consequence and Microsoft planned for.
The overall ecosystem migration is not simple because of prevalence and variance in use, but it’s still a huge net positive in my eyes.
I wouldn’t call it messy. It’s planned out, and the kind of process and concerns most senior devs are familiar with from any kind of tech migration. It’s pretty clear with clear and well-defined concerns and solutions in my eyes.
Right and the only issue is with 3rd parties which will eventually migrate as well. Basically we’re not in a hurry and migration should happen eventually.
EEE Microsoft never left.
This has nothing to do with EEE.
This is literally the Extend part, as they are altering XML standards.
No, they are changing the .sln-format, which is only used by Visual Studio itself
My initial partial read of the headline had me thinking the same way, but this is their own garbage and they can change it all they like I suppose.
The issue is that they already monopolized code editors and this is the vendor lock in move to keep people there.
I’m not quite sure why you’re being downvoted for this. I don’t use VS Code at all, but they have done a good job of getting VS Code to be extremely used and have made the predictable steps to prevent the open source versions from being equivalent/compatible, mostly by restricting the extensions.
