Hacker News new | ask | show | jobs
by folkrav 1871 days ago
I tend to agree with this POV. However, even I have to admit that VS Code (which this IDE is based on) is pretty much the poster child of Electron done right. For many languages it's quite literally IDE level of functionality, for less resources than most IDEs I've worked with (especially looking at you, JetBrains), extensions included. Of course YMMV, but it's been working pretty well for me. Hell, I've already had Slack take more resources (depending on the project).

(Now waiting for people telling me their vim setup works fine for them)

3 comments

> especially looking at you, JetBrains

JetBrains IDEs are an order of magnitude smarter than anything VSCode provides.

Depends on the language/plugin. They seem to prefer their own plugins instead of using LSP and tools given by the language ecosystem and they often end up with vastly incorrect error highlighting and autocomplete. At least this is what I saw in the Scala and Rust plugins (Scala finally got damn good but it took many years).
My completions/auto-imports/refactoring/debugging workflow is more or less identical in VS Code and PyCharm for JS/TS stuff. Python it's so-so. The golang plugin has pretty good integration for all that stuff too.

I pretty explicitly said that some languages are doing better than others. Of course a language specific IDE will probably do a better job than a generalist one in most cases.

JetBrains IDEs provide a huge amount of functionality that VSCode doesn’t, so it’s not really fair to compare them.
JetBrains also makes most Electron apps look downright parsimonious when it comes to resource usage. Hopping over to my work laptop, mine is consuming 3.21G of memory idle.
Let's compare industrial grade IDE with state of the art inspections and refactoring capabilities to music players and chat clients.
> For many languages

It's perfectly fair to compare them for some languages (mostly web). Let's also not pretend like people aren't comparing vim and ST with VSC all the time, while they're very different products.

Not when one tries to compare similar workflows in SublimeText vs VSCode.

Unfortunely most rather get the free beer VSCode, so here we stand.

Last I tried setting up LSP in ST, it kinda blew. Tons of manual, machine specific configs. No debugging, refactoring...

From my POV they are _not_ comparable.

Indeed, ST wipes the floor of VSCode regarding performance, not comparable indeed.

Unfortunely, free beer is where most plugins end up being.