5 ms·

Serious question: What's keeping people who are frustrated with Sublime Text from switching to VS Code or Atom?

by netule 9y ago

penpapersw 9y ago
In my experience having switched from using one IDE to another a few times, the difficulty for me is usually that both IDEs do 90% of what I need perfectly (after a few days of tweaking), but the other 10% feels is missing and feels critical, and in particular, neither have the same 10% missing. So I kind of have to ask myself, "which critical features am I okay with giving up?" and I can't decide so I just stick with what I know and have muscle-memory for.
- bsimpson 9y ago
  I'm trying VSCode now, but I still switch back to Sublime for SublimeGit. It's such an integral part of my workflow, and VSCode's built-in git is no substitute.
  - komali2 9y ago
    I haven't tried sublimeGit - what's it got that I'm missing from VSCode's git? I only really use it to commit and compare when I'm merging.
    - bsimpson 9y ago
      - You can easily see the status of each file (new, modified, or staged). - You can easily stage all files, each file, or just specific hunks of specific files. - You can stash and pop stashes. - You can amend a commit. - You can do all of that from the keyboard, without touching the mouse. I imagine you can do many of those things with VSCode, but it's so effortless in Sublime. I haven't learned the same workflow in VSC yet, and since I do all of those things frequently, I'm really attached to SublimeGit.
  - penpapersw 9y ago
    In the same way, I use VS Code mostly now (for node stuff) but I still load up Emacs and use Magit whenever I need to do serious version control, meaning basically anything more than just "glance at the changes and commit everything."
spamizbad 9y ago
Latency and speed probably. VS Code and Atom are awesome editors in their own respect, but not quite as snappy... yet.
- coldtea 9y ago
  Not quite as snappy ...ever. One is C++, the other are hogging memory like crazy with Electron and a whole DOM.
  - komali2 9y ago
    I'm wondering if this is why Chrome and VScode run horribly funky on every ubuntu installation I've tried. Bad memory management with so many v8 instances running?
koolba 9y ago
Atom is terribly slow and they just don't know about VS Code.
- ruleabidinguser 9y ago
  Isn't atom the less popular one
  - bousaid 9y ago
    No, Atom is more popular. VSCode is gaining momentum though. I just switched to it yesterday actually.
yflu 9y ago
If they're frustrated with Sublime with practical reasons (i.e. performance, plugins, extensibility), I don't think Code or Atom would satisfy them any better. You could make the argument for vim or emacs there, but those have been around much longer than Sublime, I doubt Sublime's eating much into those users in the first place. If they're frustrated with Sublime due to not being FOSS, nothing I guess. But again, those people would have largely switched over already.
iand 9y ago
Stupid little things mostly (I've not tried Atom but used VS Code for a while): - sublime allows projects to have multiple different folders of files, vs code forces you to use a single folder - large file support is unparalleled (excluding less etc) - reliability, in nearly a decade(?) of using sublime I've never lost edits in a file or corrupted one - it's general purpose so I can open anything, whereas vs code/atom seem more IDE-like (I know they can open anything, it's just my impression)
- ticklemyelmo 9y ago
  Just FYI, #2 was addressed in the latest update, and works well in my experience (open a 130M text file and jump to end in <5s). #1 is available in the current preview build.
joeblau 9y ago
The Electron runtime (JavaScript). I work on projects that load files that are tens/hundreds of thousands of lines. No Electron based apps can handle that without choking and crashing. Electron is decent for smaller files and it's got a great ecosystem, but they are definitely not optimized for performance.
- zeroxfe 9y ago
  Just FYI, the most recent version of vscode supports huge files. (I agree in general about Sublime performance vs Electron -- Sublime is way more responsive.)
- qmarchi 9y ago
  Atom recently moved parts of the large file rendering to some C-ish. Performance has increased monumentally.
coldtea 9y ago
I've tried both. Atom is a slow, hog, non-starter. VS Code is almost comfortable to work with, and has more plugin polish, but it's in this "slow enough to be annoying and will never be fixed as long as its based on Electron" plateau for me too.
dabockster 9y ago
Probably Electron. Even on VS Code (which is a fantastic Electron program), the Electron framework has it's limits. One huge irk I have with Electron is the amount of bloat it gives to even the most well written programs. With the VS Code example from before, no matter how well it performs, I always feel like I'm eating a stuffed crust pizza when I use it. Electron gives it much more cruft than needed. I am currently debating on whether or not to switch back to Sublime since I'm getting sick of people using Electron as an easy way of building "quality" software.
mamcx 9y ago
I like how visually look VS Code, not only the app but the syntax. But in fact, I use both. I always use 2-3 different editors. Mainly because using 2 monitors is easier to switch between apps than between tabs/windows of a app! So I use sublime to code and VS Code to visually something else. Or to write random stuff. I have the same setup before with TextMate + Sublime.

Serious question: What's keeping people who are frustrated with Sublime Text from switching to VS Code or Atom?

by netule 9y ago

Serious question: What's keeping people who are frustrated with Sublime Text from switching to VS Code or Atom?

In my experience having switched from using one IDE to another a few times, the difficulty for me is usually that both IDEs do 90% of what I need perfectly (after a few days of tweaking), but the other 10% feels is missing and feels critical, and in particular, neither have the same 10% missing. So I kind of have to ask myself, "which critical features am I okay with giving up?" and I can't decide so I just stick with what I know and have muscle-memory for.

bsimpson 9y ago
I'm trying VSCode now, but I still switch back to Sublime for SublimeGit. It's such an integral part of my workflow, and VSCode's built-in git is no substitute.
- komali2 9y ago
  I haven't tried sublimeGit - what's it got that I'm missing from VSCode's git? I only really use it to commit and compare when I'm merging.
  - bsimpson 9y ago
    - You can easily see the status of each file (new, modified, or staged). - You can easily stage all files, each file, or just specific hunks of specific files. - You can stash and pop stashes. - You can amend a commit. - You can do all of that from the keyboard, without touching the mouse. I imagine you can do many of those things with VSCode, but it's so effortless in Sublime. I haven't learned the same workflow in VSC yet, and since I do all of those things frequently, I'm really attached to SublimeGit.
- penpapersw 9y ago
  In the same way, I use VS Code mostly now (for node stuff) but I still load up Emacs and use Magit whenever I need to do serious version control, meaning basically anything more than just "glance at the changes and commit everything."

spamizbad 9y ago

Latency and speed probably. VS Code and Atom are awesome editors in their own respect, but not quite as snappy... yet.

coldtea 9y ago
Not quite as snappy ...ever. One is C++, the other are hogging memory like crazy with Electron and a whole DOM.
- komali2 9y ago
  I'm wondering if this is why Chrome and VScode run horribly funky on every ubuntu installation I've tried. Bad memory management with so many v8 instances running?

koolba 9y ago

Atom is terribly slow and they just don't know about VS Code.

ruleabidinguser 9y ago
Isn't atom the less popular one
- bousaid 9y ago
  No, Atom is more popular. VSCode is gaining momentum though. I just switched to it yesterday actually.

yflu 9y ago

If they're frustrated with Sublime with practical reasons (i.e. performance, plugins, extensibility), I don't think Code or Atom would satisfy them any better. You could make the argument for vim or emacs there, but those have been around much longer than Sublime, I doubt Sublime's eating much into those users in the first place. If they're frustrated with Sublime due to not being FOSS, nothing I guess. But again, those people would have largely switched over already.

iand 9y ago

Stupid little things mostly (I've not tried Atom but used VS Code for a while): - sublime allows projects to have multiple different folders of files, vs code forces you to use a single folder - large file support is unparalleled (excluding less etc) - reliability, in nearly a decade(?) of using sublime I've never lost edits in a file or corrupted one - it's general purpose so I can open anything, whereas vs code/atom seem more IDE-like (I know they can open anything, it's just my impression)

ticklemyelmo 9y ago
Just FYI, #2 was addressed in the latest update, and works well in my experience (open a 130M text file and jump to end in <5s). #1 is available in the current preview build.

joeblau 9y ago

The Electron runtime (JavaScript). I work on projects that load files that are tens/hundreds of thousands of lines. No Electron based apps can handle that without choking and crashing. Electron is decent for smaller files and it's got a great ecosystem, but they are definitely not optimized for performance.

zeroxfe 9y ago
Just FYI, the most recent version of vscode supports huge files. (I agree in general about Sublime performance vs Electron -- Sublime is way more responsive.)
qmarchi 9y ago
Atom recently moved parts of the large file rendering to some C-ish. Performance has increased monumentally.

coldtea 9y ago

I've tried both. Atom is a slow, hog, non-starter. VS Code is almost comfortable to work with, and has more plugin polish, but it's in this "slow enough to be annoying and will never be fixed as long as its based on Electron" plateau for me too.

dabockster 9y ago

Probably Electron. Even on VS Code (which is a fantastic Electron program), the Electron framework has it's limits. One huge irk I have with Electron is the amount of bloat it gives to even the most well written programs. With the VS Code example from before, no matter how well it performs, I always feel like I'm eating a stuffed crust pizza when I use it. Electron gives it much more cruft than needed. I am currently debating on whether or not to switch back to Sublime since I'm getting sick of people using Electron as an easy way of building "quality" software.

mamcx 9y ago

I like how visually look VS Code, not only the app but the syntax. But in fact, I use both. I always use 2-3 different editors. Mainly because using 2 monitors is easier to switch between apps than between tabs/windows of a app! So I use sublime to code and VS Code to visually something else. Or to write random stuff. I have the same setup before with TextMate + Sublime.