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

The Era of Visual Studio Code

blog.robenkleene.com

Post reply on HN
Print view View original

171–180 of 698 posts

Re: The Era of Visual Studio Code

#171

Post by kamhh94 »

vixit wrote: post #105
frankjr wrote: post #52

I completely switched to VS Code once I discovered the remote development feature [0]. It allows you to run VS Code locally but work on a project in a different environment (via SSH, Docker, WSL). The integration is seamless - search, debugger, terminal, extensions - everything looks and behaves as if it was running locally but is delegated to the configured remote. You can even have different remotes opened at the s…

Ooh, if IntelliJ gets remote functionality I'll be very happy.

I spoke to the team in KubeCon last year and they said “our research team is looking into it” with a hand wave. I doubt IntelliJ will actually implement this anytime soon, sadly.

Re: The Era of Visual Studio Code

#172

Post by catern »

xxpor wrote: post #119
necubi wrote: post #102

Earlier quoted context omitted.

Not to be that guy, but emacs has had this for years via tramp.

As someone who used tramp and switched to VS Code, it's absolutely not the same thing. The difference is plugins work on the remote side of the connection without having to be aware they're in a remote connection. VS Code makes this work by having an agent running on the remote host. For the first time I actually got autocomplete and code jumping working without a horrendous amount of effort.

This is also true with TRAMP. Anything in core Emacs, and any package outside it that isn't aggressively poorly written, works transparently with TRAMP. The core utilities for interacting with the OS such as start-file-process are all TRAMP-aware. (Or more specifically, TRAMP provides file handlers which customize start-file-process)

Re: The Era of Visual Studio Code

#173

Post by drdaeman »

andrewstuart wrote: post #21

I'm not a fan of VS Code because everything is a plugin. And plugins are inconsistent, buggy, inconsistently documented, hard to use and find and update and goodness knows who developed them. Plugins can be duplicated, outdated, abandoned and incompatible. But worst of all, a big pile of plugins isn't a consistent integrated product vision. I gave VSCode a solid go, and I had to keep installing plugin after plugin, b…

I think it's the core product values for me.

JetBrains IDEs are development environments, meant for editing code, in specific primary language. They really try their best to understand code that user works on (which is a hard problem, because code is frequently invalid while it's being actively edited), and make it as convenient as possible.

VSCode is - in my understanding - essentially, a step over older glorified extensible notepads on steroids. Unlike those older extensible notepads, it does have built-in programming language editing features, but mostly it's still not the core product but rather a job for extensions and language servers to fill that niche.

So for me VSCode wins over editors like Sublime or Atom, that don't have core programming language processing concepts baked in, but still loses to the specialized IDEs where specific language support is a primary feature (like PyCharm or GoLand).

Re: The Era of Visual Studio Code

#174

Post by untog »

altdatathrow wrote: post #127
enlyth wrote: post #83

Earlier quoted context omitted.

People like to bash VS code performance, but try opening a 60MB JSON file in different editors on Windows for example. Notepad doesn't even load and crashes, Sublime will takes minutes to even load the file, Notepad++ will be unusable as scrolling will take a few seconds, and in VS Code it opens immediately and you can seamlessly scroll to any one of the 600k lines without any delay.

fwiw, I have the opposite experience with JSON files and sublime vs. vscode. Sublime opens fast and seamless, VSCode basically ceases to operate while it struggles to figure out syntax highlighting of such a "massive" file. I have near barebones installs of both, I do not believe it's plugins nor settings related. Ultimately VSCode is my daily driver but I use sublime3 when I need to do fluid text editing, anything c…

That’s surprising, in that situation my VS Code tells me that it’s turned off syntax highlighting because the file is too large.

Re: The Era of Visual Studio Code

#175

Post by untog »

macinjosh wrote: post #156

If you want a text editor with longevity try vim or emacs. They aren't dependent on the benevolence of a greedy corporation. Over time VSCode _will_ be raided by the bean counters at MS and it will begin to track you, give you ads about MS products, and lock you in to their ecosystem. I'll never understand why a professional developer would give so much influence over their work to the likes of MS, JetBrains, etc. Su…

I don’t really understand “influence over your work” here. I agree that there’s a possibility MS will add some kind of monetisation I don’t like in the future... at which point I’ll switch editors.

But as it is, I’m much faster and efficient using VS Code than I am using Vim. It is in no way a “toy”. And it doesn’t influence my work. It’s a text editor!

Re: The Era of Visual Studio Code

#176

Post by jvalencia »

Drdrdrq wrote: post #62
ClikeX wrote: post #45

Earlier quoted context omitted.

I open a new window for each project, so I don't share this pain.

This. I wasn't even aware I could use a single window, need to look it up.

I've done this, but the performance tanks over several large projects --- this doesn't happen in separate windows.

Re: The Era of Visual Studio Code

#177

Post by cutler »

syshum wrote: post #137
andrewstuart wrote: post #111

Earlier quoted context omitted.

I'd be more interested in VSCode if Microsoft's strategy was to relentlessly implement the most popular plugins into VSCode natively such that the most commonly used and needed functions were built in and did not require plugins. The problem with systems that are really just frameworks for other to build on is they become reluctant to build stuff that plugins exist for. The philosophy becomes to depend on the plugins…

This is the difference between an opinionated vs non-opinionated IDE You seem to prefer opinionated, where other people like the fact they can pick and choose from various plugins to my their IDE their own, and if they do not like the default implementation of a feature there likely is another plugin that may work for them. For example there are a couple of git plugins, all of them act slighty different based on the…

I thought that until I realised IntelliJ Ultimate is really IntelliJ + WebStorm + PHPStorm + RubyMine + PyCharm + Goland and with plugins you're covered for most major PLs except C,C++ and C# which require 2 separate IDEs.

Re: The Era of Visual Studio Code

#178

Post by bitwize »

jimbokun wrote: post #149
TeMPOraL wrote: post #76

Earlier quoted context omitted.

Use Emacs - it's a big pile of stuff that's very well integrated, because the platform lends itself to deep interoperability - thanks to a strong conceptual model and extreme reprogrammability. :). Jokes aside, I guess what VS Code needs is to grow a strong community of people who care about the editor as much as what they do using it. Emacs has managed to do that, so it's possible.

It seems like Emacs shares the same product philosophy of VS Code. Outside of the core functionality everything is an ELisp/Javascript plugin. That explains Emacs amazing longevity, but as the article points out, Emacs longevity is actually a problem as its keyboard and UI conventions predate the modern conventions that came with Windows and MacOS.

The difference between VSCode and Emacs is the difference between an extensible text editor, and an editor that was designed to be extended, molded, and shaped as you work. At any time within Emacs, you can evaluate Lisp code to extend or modify its functionality. What's more, the always-on presence of Lisp turns Emacs into a computing environment with strong editing primitives, rather than a text editor with stuff bolted onto it. I use it to automate tedious tasks, where it serves as a sort of Lisp-programmable super-shell that can ingest data from processes and network connections into buffers, as well as the inverse, all under the control of a powerful programming language.

Re: The Era of Visual Studio Code

#179

Post by lostmsu »

Clubber wrote: post #60
lostmsu wrote: post #51

Earlier quoted context omitted.

VS 2019 without ReSharper does not feel bloated at all.

I'm running VS2019 inside a VM on a Mac and it's horrendous, particularly compile times. It does feel normal on a proper Windows box though.

I see no reason for the compile times to be different. Windows is known for slows file system access though.

Re: The Era of Visual Studio Code

#180

Post by stephc_int13 »

I've used almost all popular editors for years, Vim, Emacs, Ultraedit, Sublime and of course VSCode.

But I switched back to Sublime about six months ago.

VSCode is mostly impressively good, it is even quite fast for an electron app. But still, not as fast as Sublime, and I think it degraded at some point, and I could sense it during work.

And then, I might be a bit paranoid but I think that VSCode could be used as a kind of trojan horse by Microsoft.

I don't want a future where everything is on the cloud, including all my tools and files.

Post reply on HN