4 ms·

I really want to like Sublime (it's so fast, I like the minimal UI), but VS Code has so much inertia, and does so much out of the box or with minimal extra effo

I really want to like Sublime (it's so fast, I like the minimal UI), but VS Code has so much inertia, and does so much out of the box or with minimal extra effort that it's hard to not use it instead. At the end of the day, I have things to get done, I'm not here to tinker with tools. Same reason I never got into vim/emacs etc as a daily driver.

andrepd 2y ago
Well that is my rationale for working with Sublime instead of VScode!
- dguest 2y ago
  That's also why I use emacs. It was the first text editor I learned.
zelphirkalt 2y ago
Emacs and Neovim are things one gets into in ones free time and gets good enough to make the switch at some point at the job. Of course that is mostly only feasible, if the projects at the job are set up in a tool agnostic way or choice exists in the first place. I also want to like Sublime, but I already have a well configured Emacs and I like using free/libre software. While Sublime was great when I used it in the past, I am not sure I would use it much, since I use Emacs all day now. But the reason for Sublime over VS code is, that it is way less bloated and not running in a browser. Would need to see a direct comparison, but wouldn't be surprised, if it showed to be way snappier. If one does not need lots of specifically VS code features, I think Dublime gets out of ones way and lets you get shit done.
- diggan 2y ago
  > Emacs and Neovim are things one gets into in ones free time and gets good enough to make the switch at some point at the job. I'd probably never end up proficient with vim (and today neovim) if I didn't do the complete opposite of this and forced myself to use it for real work directly. True, I went a bit slower for one/two weeks, but if you really have to use something foreign for most of your work, you'll learn it really quickly, as long as you're up for looking things up as you go along. Of course, YMMV and all that yadda yadda.
  - mufasachan 2y ago
    I would be curious to know how you managed to do this. I really tried to do this but the tons of dev tools I am using was too much for transitioning to neovim for my daily work. Namely, I need a DAP, multiple dev tools (lsps, linters, formatters) because I work with several projects which do not have the same tools[^1]. Luckily, I do not mix multiple programming languages. Plus, I containerize all my dev env. There might be some elements missing, but the point is the number of tools is overwhelming and it makes me think that I should do the whole configuration/setup on my free time. Did you face similar issues? If yes, how did you solve them? Or maybe your work does not need that much tools? Or you have been more minimalistic than me for the number of features to be included in the neovim configuration? [1]: I work in R&D, I need to tweak and contribute in many papers code or different toolboxes/frameworks on top of the team projects.
    - tcoff91 2y ago
      LSP and formatter were really fast to set up. I used kickstart.nvim to get started and lsp and formatter are already mostly configured. DAP is trickier to set up but is doable. How often are you really debugging though? In the beginning just run both neovim and your ide and just switch when you debug. Back when LSP wasn’t a thing I still used vim but would just switch to an IDE when I needed to go code exploring and needed to be able to jump to definition and stuff like that. Wasn’t a big deal and was worth it to use both tools because vim is such a superior method for editing text.
      - mufasachan 2y ago
        Thank you for your answer. Some code base have chaotic execution path through a monolithic code base (by design). So, for these code bases, I heavily rely on the debugger. But I like your suggestion to use both of them, I think it's a good way to transition slowly and efficiently.
        tcoff91 2y ago
        Another good way to transition is to use your editor's vim plugin. Pretty much every IDE has a vim plugin that's at least adequate. I've had good experiences with vscode, jetbrains, and visual studio vim plugins.
- VHRanger 2y ago
  I would include helix in the list with nvim nowadays. The LSP support is native and very easy to set up for most languages.
- iforgot22 2y ago
  Yeah, I got used to vim while I was in school and probably wouldn't have put in the investment otherwise. It was worth. I'm not an expert in it, nor do I have a ton of fancy things installed, but it's fast and works in basically any situation (esp over SSH). My coworkers keep getting forced to change IDEs while I stick with vim.
wuliwong 2y ago
I didn't want to switch to VS Code and kinda did b/c there is less friction when I'm using the same tools as my counterparts. I like VS Code just fine. My first true love was textmate tbh. :)
deleted 2y ago
[deleted]
james2doyle 2y ago
I hear you. I think that is why I prefer Helix to Neovim when it comes to editors in terminals. There is a lot that is just done and there are sane defaults. I think the default Sublime experience is pretty slim and trim. Maybe too much for some but just right for me
buu700 2y ago
Same, after a certain point (for TypeScript particularly) I found it was too big a hassle not to switch to VS Code. All these years later, I still have VS Code configured to look and behave like Sublime. I found it funny one time when someone noticed me working on my laptop in public and said it was nice to see another Sublime user, which I had to correct him on.

andrepd 2y ago

Well that is my rationale for working with Sublime instead of VScode!

dguest 2y ago
That's also why I use emacs. It was the first text editor I learned.

zelphirkalt 2y ago

Emacs and Neovim are things one gets into in ones free time and gets good enough to make the switch at some point at the job. Of course that is mostly only feasible, if the projects at the job are set up in a tool agnostic way or choice exists in the first place. I also want to like Sublime, but I already have a well configured Emacs and I like using free/libre software. While Sublime was great when I used it in the past, I am not sure I would use it much, since I use Emacs all day now. But the reason for Sublime over VS code is, that it is way less bloated and not running in a browser. Would need to see a direct comparison, but wouldn't be surprised, if it showed to be way snappier. If one does not need lots of specifically VS code features, I think Dublime gets out of ones way and lets you get shit done.

diggan 2y ago
> Emacs and Neovim are things one gets into in ones free time and gets good enough to make the switch at some point at the job. I'd probably never end up proficient with vim (and today neovim) if I didn't do the complete opposite of this and forced myself to use it for real work directly. True, I went a bit slower for one/two weeks, but if you really have to use something foreign for most of your work, you'll learn it really quickly, as long as you're up for looking things up as you go along. Of course, YMMV and all that yadda yadda.
- mufasachan 2y ago
  I would be curious to know how you managed to do this. I really tried to do this but the tons of dev tools I am using was too much for transitioning to neovim for my daily work. Namely, I need a DAP, multiple dev tools (lsps, linters, formatters) because I work with several projects which do not have the same tools[^1]. Luckily, I do not mix multiple programming languages. Plus, I containerize all my dev env. There might be some elements missing, but the point is the number of tools is overwhelming and it makes me think that I should do the whole configuration/setup on my free time. Did you face similar issues? If yes, how did you solve them? Or maybe your work does not need that much tools? Or you have been more minimalistic than me for the number of features to be included in the neovim configuration? [1]: I work in R&D, I need to tweak and contribute in many papers code or different toolboxes/frameworks on top of the team projects.
  - tcoff91 2y ago
    LSP and formatter were really fast to set up. I used kickstart.nvim to get started and lsp and formatter are already mostly configured. DAP is trickier to set up but is doable. How often are you really debugging though? In the beginning just run both neovim and your ide and just switch when you debug. Back when LSP wasn’t a thing I still used vim but would just switch to an IDE when I needed to go code exploring and needed to be able to jump to definition and stuff like that. Wasn’t a big deal and was worth it to use both tools because vim is such a superior method for editing text.
    - mufasachan 2y ago
      Thank you for your answer. Some code base have chaotic execution path through a monolithic code base (by design). So, for these code bases, I heavily rely on the debugger. But I like your suggestion to use both of them, I think it's a good way to transition slowly and efficiently.
      - tcoff91 2y ago
        Another good way to transition is to use your editor's vim plugin. Pretty much every IDE has a vim plugin that's at least adequate. I've had good experiences with vscode, jetbrains, and visual studio vim plugins.
VHRanger 2y ago
I would include helix in the list with nvim nowadays. The LSP support is native and very easy to set up for most languages.
iforgot22 2y ago
Yeah, I got used to vim while I was in school and probably wouldn't have put in the investment otherwise. It was worth. I'm not an expert in it, nor do I have a ton of fancy things installed, but it's fast and works in basically any situation (esp over SSH). My coworkers keep getting forced to change IDEs while I stick with vim.

wuliwong 2y ago

I didn't want to switch to VS Code and kinda did b/c there is less friction when I'm using the same tools as my counterparts. I like VS Code just fine. My first true love was textmate tbh. :)

deleted 2y ago

[deleted]

james2doyle 2y ago

I hear you. I think that is why I prefer Helix to Neovim when it comes to editors in terminals. There is a lot that is just done and there are sane defaults. I think the default Sublime experience is pretty slim and trim. Maybe too much for some but just right for me

buu700 2y ago

Same, after a certain point (for TypeScript particularly) I found it was too big a hassle not to switch to VS Code. All these years later, I still have VS Code configured to look and behave like Sublime. I found it funny one time when someone noticed me working on my laptop in public and said it was nice to see another Sublime user, which I had to correct him on.