this post was submitted on 19 Mar 2025
32 points (100.0% liked)

Programming

19076 readers
159 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
top 9 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 3 days ago* (last edited 3 days ago) (1 children)

🤷 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.

[–] [email protected] 3 points 2 days ago

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.

[–] [email protected] 2 points 2 days ago (2 children)
[–] [email protected] 3 points 2 days ago (1 children)

This has nothing to do with EEE.

[–] [email protected] 1 points 1 day ago (1 children)

This is literally the Extend part, as they are altering XML standards.

[–] [email protected] 5 points 1 day ago

No, they are changing the .sln-format, which is only used by Visual Studio itself

[–] [email protected] 5 points 2 days ago (1 children)

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.

[–] [email protected] 2 points 2 days ago (1 children)

The issue is that they already monopolized code editors and this is the vendor lock in move to keep people there.

[–] [email protected] 4 points 1 day ago

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.