Visual Studio Code is designed to fracture
ghuntley.com
Visual Studio Code is designed to fracture
1–10 of 149 posts
Re: Visual Studio Code is designed to fracture
#2"The move affects millions of developers, as the Python extension is by far the most popular tool in the VS Code Marketplace"
One of the reasons to use Emacs is to avoid asking Microsoft for permission to code.
Re: Visual Studio Code is designed to fracture
#3This is what happens when you build software on another company's platform. Why put your time making plugins for VS Code when rug can be pulled from under any time?
Re: Visual Studio Code is designed to fracture
#4This is what happens when you build software on another company's platform. Why put your time making plugins for VS Code when rug can be pulled from under any time?
The same could be said about many other platforms: Apps for iPhones and android, chrome and Firefox extensions. Yet people still write them, and some get screwed when their app or extension is removed or doesn’t evolve to the next API change.
Re: Visual Studio Code is designed to fracture
#5[deleted]
Re: Visual Studio Code is designed to fracture
#6I had to use VS Code it briefly for a class, and was kind of shocked by the telemetry stuff, and that it's just ignore-accepted by both the students and the instructors.
But what turned me off more was this janky feeling around the whole application, something I don't remember experiencing in many other Microsoft tools, such as VB. It feels like it was designed from the code up rather than from the interface down, and everything I do feels like I'm accommodating the program rather than the other way around.
Anyway, the author of this article was right, I still did have it installed in my dev environment, left behind from those classes. I decided to use this opportunity to `pacman --remove code`.
The situation with bad application behaviors being "baked into the code" and propagating to all the "free" distributions is very sad, similar to what's happening with both Chrome and Firefox.
For example, HSTS is now baked into the all the standard distributions and there's absolutely no way (that I've found) to turn it off. I understand the "security" reasons behind it for regular users, but as someone mindful and often completely unable to access a website only because their certificate has expired, I am quite miffed.
Re: Visual Studio Code is designed to fracture
#7This is rather scary and disheartening. I finally switched from 12+ years of Eclipse to vscode just last year. After a disproportionate amount of hand wringing and testing. I'd rather move houses twice before moving to a new IDE. But it's true that since running VSCode I feel less like I actually own my environment. I would never rent an IDE or do my work in the cloud, just on basic principle. I really like VS now that I've wrangled it, though, and I'm hoping to not have to bail and find a new platform in the next 10 years or so.
Re: Visual Studio Code is designed to fracture
#8This is what happens when you build software on another company's platform. Why put your time making plugins for VS Code when rug can be pulled from under any time?
The same could be said about many other platforms: Apps for iPhones and android, chrome and Firefox extensions. Yet people still write them, and some get screwed when their app or extension is removed or doesn’t evolve to the next API change.
I have grown to appreciate HTML and the Web for this reason. If done carefully, one can write an application which is accessible to dozens of different client software and hardware options, and no one vendor can screw you over.
Re: Visual Studio Code is designed to fracture
#9As far as I understand, it's not a big deal as this is sort of the dumb end of the IDE- just the text editor part, not the compiler or debugger. Correct me if I'm wrong. I don't know why anyone would bother using a microsoft text editor on linux, but if you are using windows you're already getting screwed pretty hard with telemetry
If a windows-using colleague asks me what text editor to use, I just tell them to use notepad++ or geany. The hard part is moving them away from MSVSC++ to some command-line compiler or debugger (like msys/mingw) so they can make reliable/extensible build scripts.
Re: Visual Studio Code is designed to fracture
#10This is what happens when you build software on another company's platform. Why put your time making plugins for VS Code when rug can be pulled from under any time?
True but the alternative is rolling and maintaining every aspect of your environment yourself. Build environments in particular. If you even have that kind of time, you have to weigh it against shipping a product.