[Hamuko]

What's the actual difference? As far as I can see, they're both poor text editors with bad interfaces, built on top of the horrible mess that is Electron. They're also both massive. VS Code takes up 235 MB and Atom takes a whopping 530 MB. Sublime Text is like 30 MB.

[SippinLean]

>with bad interfaces

VS Code's interface is nearly identical to Sublime's, with some nice sugar in places that are helpful (optional GUI for keybindings and extensions).

For debugging and version control VS Code's interface OOTB is leaps and bounds above Sublime's.

>VS Code takes up 235 MB

Meh I have 16GB of RAM on my old computer. Or do you actually just mean HDD space? Who cares about 200MB in that regard?

[Hamuko]

VS Code's interface is a garbage Metro (or whatever Microsoft is calling it today) implementation with sidebar hell from Office.

>Who cares about 200MB in that regard? Who cares about anything? Just use everything you have. CPU, RAM, battery life and so on. These things are free for the developer.

Is VS Code actually seven times better and/or complex compared to Sublime Text that it actually needs to use the additional disk space.

Electron is garbage and just an exercise in providing a bad user experience to people for the sake of making front-end developers happy since they're the ones making them. The end result is bloated applications that are slow and use way too much system resources. VS Code used to use a significant portion (>10%) of the CPU just to draw a blinking cursor.

[LiquidFlux]

Electron is the reason you're getting these kind of desktop applications built in the first place, it's opened up an entire portal of developers to catering to your needs.

It may not be the ultimate solution to the problem with regards to things such as performance, but these are irrelevant if the application were to never be built in the alternative.

[swozey]

Cheers to that. Maybe now with Electron the developers at 1Password will give us a Linux port........

[SippinLean]

All vague overly general misrepresentations of the very specific points I made. I think the other "DAE Electron is bad?" comments can suffice without you adding.

[oblio]

> they're both poor text editors with bad interfaces

I can see why you might call them "poor text editors", probably based on real or perceived performance issues.

But I don't see why "bad interfaces"...

[edraferi]

> What's the actual difference?

I believe Intellisense is VScode's best differentiator. It provides very good autocomplete.

[rspeer]

I use VScode currently (for Python) but I'm not entirely satisfied with it.

How do you set up this very good autocomplete? The official Python plugin (by Don Jayamanne) seems kind of bad at autocomplete and related features. I get autocomplete that:

- Autocompletes random stuff because I pressed "enter" or "down"

- Tries to autocomplete comments

- If I tell it to autocomplete only on tab, then it will sometimes autocomplete and sometimes insert spaces; the faster I type, the more I get spaces

- Pops up enormous tooltips for function docstrings that are taller than my entire code window

[drej]

Is the editor size an issue? For quick startup, sure, but when the tool is actually running? (Which at least on my machine, it's on most of the day anyway.)

I used to prefer lean editors (vim, Sublime), but then intellisense and plugins of VS Code won me over. That and git support and other niceties working out of the box.

[petre]

> they're both poor text editors with bad interfaces

They're not poor editors. They're okay. And the interface is fine, I've actually grown to like Atom after having used it for a month. They are they're at least an order a magnitude bigger and slower than Sublime Text, yet pretty usable on a modern desktop computer. I've also used Sublime Text for three or four years on a daily basis.

[jordache]

it's funny to complain about absolute program size on the disk...