18 ms·
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 til
by 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 agoTerminal 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.