Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code is designed to fracture

ghuntley.com

Post reply on HN
Print view View original

11–20 of 149 posts

Re: Visual Studio Code is designed to fracture

#11

Post by cowtools »

forgotmypw17 wrote: post #8
TedDoesntTalk wrote: post #4

Earlier quoted context omitted.

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.

Generally true, unless that vendor is google. Manifest v3 is still in recent memory.

Re: Visual Studio Code is designed to fracture

#13

Post by noduerme »

cowtools wrote: post #9

As 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…

One reason I chose VS is because I'm a small dev shop, often working alone, and it's one of the only good IDEs around with plugins for syncing via sftp. In many cases that saves me having to use a separate client or configure cloud rollouts for minor code changes. Small devs are the target audience for vscode and also the most likely to be negatively impacted if the environment fractures.

Re: Visual Studio Code is designed to fracture

#14

Post by memco »

d0mine wrote: post #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.

Does eMacs have a good remote editing and debugging system comparable to VSC? I’ve tried pycharm and nvim, but both were clunky and did not work as well if at all for remote debugging and editing with navigation, autocomplete, linting etc. VSC does all that with very little manual configuration required.

Re: Visual Studio Code is designed to fracture

#15

Post by forgotmypw17 »

cowtools wrote: post #11
forgotmypw17 wrote: post #8

Earlier quoted context omitted.

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.

Generally true, unless that vendor is google. Manifest v3 is still in recent memory.

Yeah, it sucks what's happening with browser extensions and configurability in general. Opera 3, released in 1997, allows the user to override author styles with their own. Same for IE6, released in 2001.

But that's a different aspect of the platform -- the browser itself.

At least for the time being, on the Web side, there are so many different other browsers, that Chrome cannot break step with all of them at once.

And so if I write basic HTML and test it thoroughly, I can accommodate almost any user on any device, browser, and configuration. And this makes me very happy.

Re: Visual Studio Code is designed to fracture

#18

Post by TobyTheDog123 »

georgia_peach wrote: post #16

Here's $0.00. Take it, and buy yourself a real editor. Anything you choose to pay above that goes to needy children in Uganda. corrected per systemvoltage : https://www.vim.org/sources.php

Shift + Shift + Command + ESC + Shift + 1 + ~ + Shift + Esc + CTRL + Command + Shift + F1 + \x00 + F3 + ~

Phew! Finally back to my terminal

Re: Visual Studio Code is designed to fracture

#19

Post by skybrian »

I remember when the FSF had dire warnings about using the Sun JDK. I ignored it and kept on using Java, and nothing bad happened. The JDK was eventually GPLed, and by then I decided I didn't like Java anymore and moved on to better languages anyway.

I feel kind of the same about VS Code. Binary product? Telemetry? Centralized marketplace? Some plugins are closed source? Eh, whatever. That stuff doesn't get in my way and I suspect that nothing particularly bad will happen to developers. Someday a better IDE will become popular, perhaps built on some of the code and standards spun off by VS Code (like the language server protocol), perhaps not. This editor will do until that happens.

The politics isn't as good as I'd like, but often the politics never actually materializes as a bad user experience, despite the complaints.

Re: Visual Studio Code is designed to fracture

#20

Post by mkl95 »

I understand Visual Studio Code as a sophisticated Language Server Protocol frontend, and it generally does a good job at that. The IDE of the future will have Jetbrains grade UX with a heavy emphasis on LSP interfaces that "just work", rather than requiring some investigation about what setting needs to be set to which value and why basic stuff breaks mysteriously.
Post reply on HN