5 ms·

Obligatory comment: I really like VSCode but keep jumping back and forth between it and Sublime because of startup time. I like VSCode enough to use it daily a

Obligatory comment: I really like VSCode but keep jumping back and forth between it and Sublime because of startup time. I like VSCode enough to use it daily and extensively and jump back to sublime when I need to jump around projects fast–when startup time becomes crucial. I believe they will solve this issue at some point.

ch4s3 9y ago
I think they can probably improve, but just due to being built on chromium means a level of overhead that's likely higher than sublime. If fix means acceptably close, they might get there. I'm now using VSCode daily and have no real complaints.
Waterluvian 9y ago
By startup do you mean the initial loading of VSCode or the cost of switching project contexts within VSCode? I wonder if you can just pre-load Code and hide it in some manner plus use CLI commands to open new folders/files within the existing VSCode instance rather than a new one? I do agree, though. VSCode has so many benefits but every so often I hit an irregular usage where I'm opening lots of various stuff and its a bit slow.
lobster_johnson 9y ago
While VSCode is great, it's also useless as $EDITOR. It's very slow to start (when it's already running), and while you'd think you could speed this up by making it open a new tab in your current window and and return control the parent process when you close that tab ("code -r -w", I believe), that's not possible. It can open the new tab, but it never relinquishes control, at least not for me. Wouldn't be an issue if startup was super fast with "code -w", but creating new windows, even when VSCode is running, takes several seconds. So I still use "joe" as $EDITOR.
- Tyriar 9y ago
  > and while you'd think you could speed this up by making it open a new tab in your current window and and return control the parent process when you close that tab ("code -r -w", I believe), that's not possible. Exactly this is actually coming in v1.17.
  - lobster_johnson 9y ago
    Awesome. Of course, fast window startup would be even better.

ch4s3 9y ago

I think they can probably improve, but just due to being built on chromium means a level of overhead that's likely higher than sublime. If fix means acceptably close, they might get there. I'm now using VSCode daily and have no real complaints.

Waterluvian 9y ago

By startup do you mean the initial loading of VSCode or the cost of switching project contexts within VSCode? I wonder if you can just pre-load Code and hide it in some manner plus use CLI commands to open new folders/files within the existing VSCode instance rather than a new one? I do agree, though. VSCode has so many benefits but every so often I hit an irregular usage where I'm opening lots of various stuff and its a bit slow.

lobster_johnson 9y ago

While VSCode is great, it's also useless as $EDITOR. It's very slow to start (when it's already running), and while you'd think you could speed this up by making it open a new tab in your current window and and return control the parent process when you close that tab ("code -r -w", I believe), that's not possible. It can open the new tab, but it never relinquishes control, at least not for me. Wouldn't be an issue if startup was super fast with "code -w", but creating new windows, even when VSCode is running, takes several seconds. So I still use "joe" as $EDITOR.

Tyriar 9y ago
> and while you'd think you could speed this up by making it open a new tab in your current window and and return control the parent process when you close that tab ("code -r -w", I believe), that's not possible. Exactly this is actually coming in v1.17.
- lobster_johnson 9y ago
  Awesome. Of course, fast window startup would be even better.