1. Anything that requires an account to use is not free
2. How much longer before VS Code is web only? I give it 2 years.
Microsoft is previewing Visual Studio Code for the Web, a code editor that runs entirely in the browser. The post introducing the new service was put up yesterday but is returning "page not found" at the time of writing, so possibly was published prematurely. But it is expected to return soon, since the technology looks the …
It splits state between the local and remote processes. The latency only kicks in on save, not during ordinary text editing. Save doesn't block the UI either.
If you're in a "save, build, deploy to remote environment, test, edit" cycle then having the editor save directly to the remove environment can be a net time saving. This is my experience with AWS's equivalent thing (which I think is also based on VSCode).
"then having the editor save directly to the remove environment can be a net time saving"
I have been saying this about vi or emacs over ssh for decades. It Looks like "modern" developers are just about catching up. Minus of course being able to run debuggers, linters, cscope, doxygen, etc on a restrictive consumer web text editor.
Careful with that neckbeard chap!
There's nothing restrictive about VsCode - each to their own.
Seriously, if it was restrictive, then everyone would be using vi or emacs.
I have met very few people who can make vi or emacs "fly" like an editor such as VSCode or IntelliJ - they are a rare breed - and usually the "not invented here, not interested" types.
And heck, if you really want to, you can vim emulation for VSCode - what's not to like?
Embrace whatever tool makes your life easier - and seriously, cut it out with the quotes of "modern" developers, it's such a bullshit trope.
I know a LOT of developers in their 50's who have been coding for over 40 years - excellent developers - who just embrace whatever works for them.
No need to pigeon hole people into areas just because of your own narrow minded prejudices.
Mm. Running vi or emacs on the remote machine over ssh *does* have high UI latency during text editing. You can almost compensate for it in vi by typing ahead, but from experience it's not a fun or reliable experience.
Running VSCode in a web browser is more like using emacs tramp-mode. Edit locally, save remotely. I assume there's a vim plugin somewhere with similar functionality.
Biting the hand that feeds IT © 1998–2021