4 ms·

I don't know why you're saying they are slow. vscode starts up pretty fast. Sure it consumes more resources than vim. However having code completion, debugging,

by nojvek 10y ago

I don't know why you're saying they are slow. vscode starts up pretty fast. Sure it consumes more resources than vim. However having code completion, debugging, linting, and a bunch of IDE like features is super useful including the fact that it's cross platform and open source. It's very hackable. Just last night I fixed an issue that had been bugging me for a while. Pages with ads use a lot more of my CPU so I'm not really worried. This looks like a chrome problem more than Vscode. I do know that they take perf very seriously and this will be given some attention.

juandazapata 10y ago
100% of vim users will tell you that their vim setups also have code completion, debugging, linting, etc...
- naibafo 10y ago
  And I just proved your point. :)
- Spivak 10y ago
  Sure, but I won't pretend that adding those features doesn't add some significant resource usage and some occasional slowdown.
  - temp 10y ago
    >doesn't add some significant resource usage If by "significant" you mean less resources than opening a blank tab in Atom.
naibafo 10y ago
At least while I was using atom on a not so high end machine, it generally took a few seconds too start and being usable. Neovim on the other hand is there in a heartbeat, and I do have completion, debugging, linting, file browsing, git integration... available as well :)
fauigerzigerk 10y ago
>I don't know why you're saying they are slow. vscode starts up pretty fast I takes "ages" to start up, meaning it interrupts my workflow. I like vscode, but startup time for the app and for new windows is terrible (~2 seconds) and it's one reason why I still prefer sublime for anything that doesn't have significantly better language plugins in vscode.
- Osmose 10y ago
  I so very rarely close Atom, and generally don't use multiple windows in a single app, that those slowdowns never really bite me. It'd be interesting to see their analytics to see how often people actually hit these things in practice.
ue_ 10y ago
To be fair, Emacs can easily have code completion, debugging, linting and a bunch of IDE features, it's cross platform and it's open source. It's probably one of the most hackable editors out there. And I use adblock :)
veidr 10y ago
> I don't know why you're saying they are slow Because the slowness, when compared to a whole slate of "regular" (== non-web-browser-based) editors, is empirically measurable, and is not just like "twice as slow" or "500% less efficient", but — in many cases, for various operations, as most recently delineated by the joe's own editor benchmarks, but really I mean repeatedly demonstrated over and over for the life of these editors — hundreds of times slower or even infinitely slower (it just gives up and crashes). To a lot of people, that's infuckinsanebro!!!, like a car that gets not n miles per gallon, but needs n gallons per mile. I get that the extensibility and hackability is appealing. I like that, too. But at what cost!
- itake 10y ago
  have you used VS code? I recently switched from Sublime to VS Code. Originally, I hated the slowness. But the slow point in my work (Software engineer) is not how fast I open files, but on how easy is it for me to transfer what I am thinking to the screen. VS Code, while slow, has extensions that make me much more productive than when I was using Sublime. Highlights include: - auto-formatting my ruby code to fit coding standards. I don't have to spend time mucking with spacing. I write it the fastest way I can, and it fixes it. - inline git blame. I can easily see who and why a line of code is changed as I select each line. Super useful when debugging. I don't have to kick up the console or fire up github.com in my browser. - prettify json. I don't have to open up chrome to some json formatting tool to debug my http responses. edit: I still have to use sublime to open very large files, but that is rare in my work.
  - veidr 10y ago
    Yeah, I have, and I actually use it regularly (along with several other editors). The slowness (of not just opening files, but editing them) drives me up the wall, but in certain workflows (e.g., TypeScript) it can be worth it.

by nojvek 10y ago

juandazapata 10y ago

100% of vim users will tell you that their vim setups also have code completion, debugging, linting, etc...

naibafo 10y ago
And I just proved your point. :)
Spivak 10y ago
Sure, but I won't pretend that adding those features doesn't add some significant resource usage and some occasional slowdown.
- temp 10y ago
  >doesn't add some significant resource usage If by "significant" you mean less resources than opening a blank tab in Atom.

naibafo 10y ago

At least while I was using atom on a not so high end machine, it generally took a few seconds too start and being usable. Neovim on the other hand is there in a heartbeat, and I do have completion, debugging, linting, file browsing, git integration... available as well :)

fauigerzigerk 10y ago

>I don't know why you're saying they are slow. vscode starts up pretty fast I takes "ages" to start up, meaning it interrupts my workflow. I like vscode, but startup time for the app and for new windows is terrible (~2 seconds) and it's one reason why I still prefer sublime for anything that doesn't have significantly better language plugins in vscode.

Osmose 10y ago
I so very rarely close Atom, and generally don't use multiple windows in a single app, that those slowdowns never really bite me. It'd be interesting to see their analytics to see how often people actually hit these things in practice.

ue_ 10y ago

To be fair, Emacs can easily have code completion, debugging, linting and a bunch of IDE features, it's cross platform and it's open source. It's probably one of the most hackable editors out there. And I use adblock :)

veidr 10y ago

> I don't know why you're saying they are slow Because the slowness, when compared to a whole slate of "regular" (== non-web-browser-based) editors, is empirically measurable, and is not just like "twice as slow" or "500% less efficient", but — in many cases, for various operations, as most recently delineated by the joe's own editor benchmarks, but really I mean repeatedly demonstrated over and over for the life of these editors — hundreds of times slower or even infinitely slower (it just gives up and crashes). To a lot of people, that's infuckinsanebro!!!, like a car that gets not n miles per gallon, but needs n gallons per mile. I get that the extensibility and hackability is appealing. I like that, too. But at what cost!

itake 10y ago
have you used VS code? I recently switched from Sublime to VS Code. Originally, I hated the slowness. But the slow point in my work (Software engineer) is not how fast I open files, but on how easy is it for me to transfer what I am thinking to the screen. VS Code, while slow, has extensions that make me much more productive than when I was using Sublime. Highlights include: - auto-formatting my ruby code to fit coding standards. I don't have to spend time mucking with spacing. I write it the fastest way I can, and it fixes it. - inline git blame. I can easily see who and why a line of code is changed as I select each line. Super useful when debugging. I don't have to kick up the console or fire up github.com in my browser. - prettify json. I don't have to open up chrome to some json formatting tool to debug my http responses. edit: I still have to use sublime to open very large files, but that is rare in my work.
- veidr 10y ago
  Yeah, I have, and I actually use it regularly (along with several other editors). The slowness (of not just opening files, but editing them) drives me up the wall, but in certain workflows (e.g., TypeScript) it can be worth it.