4 ms·

Genuinely interested why you think so. Care to elaborate?

by hxii 3y ago

ilrwbwrkhv 3y ago
Sure. I can go on and on but I will keep it to 3 major reasons: 1. A restricted api for plugins. Plugins have never made the core editing experience slow. I have tried the tailwind css extension on vs code and on a very fast machine, it does something to make the auto suggestions show up / not show up / not select the top item / a mix of randomness just as one example. 2. Incredible speed. I type a key, it shows up virtually instantly. Editing and changes are "constant time". This gives me confidence. I remember the days of Eclipse and Java IDEs when you would type and after a while a whole string would get printed. While vs code isn't that bad, it still feels sluggish compared to sublime. 3. The godfather of modern text editors. Sublime championed the whole command / ctrl p to do any task. It is still superior than vs code in that. It remembers tasks and files I use often and learns what I use. The only thing better for a while with vs code was async LSP but now Sublime has caught up in that as well so there is literally no reason to use anything else.
- WhereIsTheTruth 3y ago
  VSCode builtin terminal is very nice VSCode build/task system is very nice VSCode builtin debugger is very nice VSCode remote editing is very nice There are reasons to like sublime text, but let's not ignore the strengths of VSCode, on top of being open source..
  - josephcsible 3y ago
    VSCode isn't open source. It's just built on open source. Compare it to Google Chrome being built on open source Chromium.
    - WhereIsTheTruth 3y ago
      You are right, I should have mentioned https://vscodium.com/ https://vscodium.com/
  - ilrwbwrkhv 3y ago
    Why do you need a terminal in your editor. CMD-tab to switch vs CMD-tilda to open the terminal and you get a worse experience in the editor. Same as the build system. https://packagecontrol.io/packages/Debugger https://packagecontrol.io/packages/Debugger is superior to VSCode's debugger. I use vim for remote editing but I am sure you can find something for Sublime if you really wanted to. Sublime Text also has tons of plugins by the way. Just because VS Code is built on top of open source technologies doesn't mean it's better.
    - WhereIsTheTruth 3y ago
      For the same reason you use vim in your terminal, in some cases it's nice to have, sometimes it's not, but now you have the ability and choice to do it I disagree about your statement on the debugger, I tried both Plugins and being able to edit the source of the program are 2 fundamentally different things As I explained above, I fall back to neovim because I can't stand the file previewing when you switch files in sublime text, you can't change that behavior with plugins, you need source access Another argument that you can't defeat: There is this thing with code completion popup that I so annoying in vscode, it being open source lets me fix it without having to wait for the good will of the developer to understand/fix it for me, I did it myself: https://github.com/microsoft/vscode/pull/163490 https://github.com/microsoft/vscode/pull/163490
      - ilrwbwrkhv 3y ago
        Well code completion can be customized in sublime as well. I guess if you don't like the preview feature you're out of luck. Personally I like all of sublime's features and it is fast rock solid and dependable. Vs code is clunky, slow, shaky but very extensible.
        WhereIsTheTruth 3y ago
        That's not true, and believe me I argued with the authors of the LSP plugin for the look of the completion box (look on both discord and github tracker) Example: ST: https://i.imgur.com/sozrgpv.png https://i.imgur.com/sozrgpv.png VSC: https://i.imgur.com/Jcn9ip8.png https://i.imgur.com/Jcn9ip8.png You can't make the label detail (function parameters) less bright, it requires asking for ST to implement an API wich they refuse to do, I tried ;) You choose to not want to understand, that's unfortunate The fact that you also can't even disable the auto previewing of files in sublime says it all (they refuse to let you do it, again, I asked them countless times) When I want a fast editor, I fall back to my terminal now, It not worth my time to argue with devs of a proprietary and closed code base

Genuinely interested why you think so. Care to elaborate?

by hxii 3y ago

Genuinely interested why you think so. Care to elaborate?

Sure. I can go on and on but I will keep it to 3 major reasons: 1. A restricted api for plugins. Plugins have never made the core editing experience slow. I have tried the tailwind css extension on vs code and on a very fast machine, it does something to make the auto suggestions show up / not show up / not select the top item / a mix of randomness just as one example. 2. Incredible speed. I type a key, it shows up virtually instantly. Editing and changes are "constant time". This gives me confidence. I remember the days of Eclipse and Java IDEs when you would type and after a while a whole string would get printed. While vs code isn't that bad, it still feels sluggish compared to sublime. 3. The godfather of modern text editors. Sublime championed the whole command / ctrl p to do any task. It is still superior than vs code in that. It remembers tasks and files I use often and learns what I use. The only thing better for a while with vs code was async LSP but now Sublime has caught up in that as well so there is literally no reason to use anything else.

WhereIsTheTruth 3y ago
VSCode builtin terminal is very nice VSCode build/task system is very nice VSCode builtin debugger is very nice VSCode remote editing is very nice There are reasons to like sublime text, but let's not ignore the strengths of VSCode, on top of being open source..
- josephcsible 3y ago
  VSCode isn't open source. It's just built on open source. Compare it to Google Chrome being built on open source Chromium.
  - WhereIsTheTruth 3y ago
    You are right, I should have mentioned https://vscodium.com/ https://vscodium.com/
- ilrwbwrkhv 3y ago
  Why do you need a terminal in your editor. CMD-tab to switch vs CMD-tilda to open the terminal and you get a worse experience in the editor. Same as the build system. https://packagecontrol.io/packages/Debugger https://packagecontrol.io/packages/Debugger is superior to VSCode's debugger. I use vim for remote editing but I am sure you can find something for Sublime if you really wanted to. Sublime Text also has tons of plugins by the way. Just because VS Code is built on top of open source technologies doesn't mean it's better.
  - WhereIsTheTruth 3y ago
    For the same reason you use vim in your terminal, in some cases it's nice to have, sometimes it's not, but now you have the ability and choice to do it I disagree about your statement on the debugger, I tried both Plugins and being able to edit the source of the program are 2 fundamentally different things As I explained above, I fall back to neovim because I can't stand the file previewing when you switch files in sublime text, you can't change that behavior with plugins, you need source access Another argument that you can't defeat: There is this thing with code completion popup that I so annoying in vscode, it being open source lets me fix it without having to wait for the good will of the developer to understand/fix it for me, I did it myself: https://github.com/microsoft/vscode/pull/163490 https://github.com/microsoft/vscode/pull/163490
    - ilrwbwrkhv 3y ago
      Well code completion can be customized in sublime as well. I guess if you don't like the preview feature you're out of luck. Personally I like all of sublime's features and it is fast rock solid and dependable. Vs code is clunky, slow, shaky but very extensible.
      - WhereIsTheTruth 3y ago
        That's not true, and believe me I argued with the authors of the LSP plugin for the look of the completion box (look on both discord and github tracker) Example: ST: https://i.imgur.com/sozrgpv.png https://i.imgur.com/sozrgpv.png VSC: https://i.imgur.com/Jcn9ip8.png https://i.imgur.com/Jcn9ip8.png You can't make the label detail (function parameters) less bright, it requires asking for ST to implement an API wich they refuse to do, I tried ;) You choose to not want to understand, that's unfortunate The fact that you also can't even disable the auto previewing of files in sublime says it all (they refuse to let you do it, again, I asked them countless times) When I want a fast editor, I fall back to my terminal now, It not worth my time to argue with devs of a proprietary and closed code base