3 ms·

I personally prefer version control in sublime with suitable plugins it's the debugging experience that I feel is lacking in sublime Vs vscode and atom Sublime

by slifin 9y ago

I personally prefer version control in sublime with suitable plugins it's the debugging experience that I feel is lacking in sublime Vs vscode and atom Sublime does not have the concept of panels so any kind of debugger in sublime looks and handles really bad

hit8run 9y ago
The Built-In Terminal in VSCode is something I would love to see in Sublime. For Ruby Coding this would be sufficient for me. For Go I currently prefer VSCode because of the debugging capabilities.
- stonewhite 9y ago
  Implementing a "Built-in Terminal" mindset is what is wrong with VSCode/Atom etc. You already have a terminal emulator installed in your system, and you can tile the windows if you want a terminal right under your editor. NIH syndrome of re-implementing everything under one roof is not really required, since we are heavily utilizing desktop environments for the past couple of decades, which allows you to put separate applications in one screen.
  - coldtea 9y ago
    >Implementing a "Built-in Terminal" mindset is what is wrong with VSCode/Atom etc. Electron is what is wrong with them -- if anything is. Built-in terminal has nothing to do with it. >NIH syndrome of re-implementing everything under one roof is not really required, since we are heavily utilizing desktop environments for the past couple of decades, which allows you to put separate applications in one screen. That's less streamlined than having the editor directly cater to different needs. The "separate git terminal window" for example doesn't know anything about your open files and vice versa.
    - sleepybrett 9y ago
      Terminal buffers have a long history and certainly aren't what's wrong with atom/vscode. I concur that that problem is "using a web browser as a ascii rendering engine". I think the one thing that keeps terminal buffers out of sublime text is probably it's crossplatfomness. Seems like it would be a bit of a hairball to get right on every platform.
VladTheImplier 9y ago
C++ programmer who switched from VS to Sublime here. That was the hardest part for me. Was a very hard learning curve with finding setting it all up and getting SublimeGDB and the GCC linter to work. But I'm glad I made the switch in the end. Everything from writing, to compiling is so much faster, nicer and less cluttered.

by slifin 9y ago

hit8run 9y ago

The Built-In Terminal in VSCode is something I would love to see in Sublime. For Ruby Coding this would be sufficient for me. For Go I currently prefer VSCode because of the debugging capabilities.

stonewhite 9y ago
Implementing a "Built-in Terminal" mindset is what is wrong with VSCode/Atom etc. You already have a terminal emulator installed in your system, and you can tile the windows if you want a terminal right under your editor. NIH syndrome of re-implementing everything under one roof is not really required, since we are heavily utilizing desktop environments for the past couple of decades, which allows you to put separate applications in one screen.
- coldtea 9y ago
  >Implementing a "Built-in Terminal" mindset is what is wrong with VSCode/Atom etc. Electron is what is wrong with them -- if anything is. Built-in terminal has nothing to do with it. >NIH syndrome of re-implementing everything under one roof is not really required, since we are heavily utilizing desktop environments for the past couple of decades, which allows you to put separate applications in one screen. That's less streamlined than having the editor directly cater to different needs. The "separate git terminal window" for example doesn't know anything about your open files and vice versa.
  - sleepybrett 9y ago
    Terminal buffers have a long history and certainly aren't what's wrong with atom/vscode. I concur that that problem is "using a web browser as a ascii rendering engine". I think the one thing that keeps terminal buffers out of sublime text is probably it's crossplatfomness. Seems like it would be a bit of a hairball to get right on every platform.

VladTheImplier 9y ago

C++ programmer who switched from VS to Sublime here. That was the hardest part for me. Was a very hard learning curve with finding setting it all up and getting SublimeGDB and the GCC linter to work. But I'm glad I made the switch in the end. Everything from writing, to compiling is so much faster, nicer and less cluttered.