3 ms·

vscode is interesting[0] but based on the grunts in my vicinity at work it has some serious glitches: - file tabs going somewhere (tempted to say disappearing

vscode is interesting[0] but based on the grunts in my vicinity at work it has some serious glitches: - file tabs going somewhere (tempted to say disappearing but who knows, they just evaporated) - strange workflow, git extension forbids you to edit a staged file without unstaging, requires a few click everytime - previous point hints at a slow / clickfest culture, what is transparent in magit, and also in normal git usage, needs extra disruptive steps - strange readline behavior in terminals (maybe they were inspired by emacs term madness :) - requires a modern machine (vscode is the only piece of software i've ever seen that will slow down keyboard input handling to less than 1fps. on a core i5 gen2, fresh install, empty project, empty file. that was something) being js based allows for nice things, i wonder if you can extend things on the fly without creating an extension [0] even though i love frugal and simple ui/ux, text and all that, I'm still curious about what a dom based editor can bring, in terms of stable layout for fancier information presentation while coding. Emacs buffers and GUI is quite limited here.

schemescape 4y ago
> vscode is the only piece of software i've ever seen that will slow down keyboard input handling to less than 1fps. on a core i5 gen2, fresh install Interesting! I had (sort of) the opposite experience. I loaded VS Code on an old netbook and braced myself for a horrible experience... but it was actually pretty responsive. I was honestly shocked at how well it ran, considering how slow the computer was. Sure, VS Code was definitely slower than Vim, but it was fast enough that I kept using it (for the excellent TypeScript integration).
- agumonkey 4y ago
  Interesting, my machine was really empty so I wonder what caused it to lag that much. Maybe a strange issue on that version.
blep_ 4y ago
> file tabs going somewhere I'm going to guess this is the "preview" misfeature, where if you open a file in certain ways (e.g. by jumping into it with one of the go-to-something commands) it gets opened in a weird transient state and converted to a normal tab on edit or closed on navigating away. You can turn that off.
- agumonkey 4y ago
  sounds plausible indeed, i'll notify my colleague

schemescape 4y ago

> vscode is the only piece of software i've ever seen that will slow down keyboard input handling to less than 1fps. on a core i5 gen2, fresh install Interesting! I had (sort of) the opposite experience. I loaded VS Code on an old netbook and braced myself for a horrible experience... but it was actually pretty responsive. I was honestly shocked at how well it ran, considering how slow the computer was. Sure, VS Code was definitely slower than Vim, but it was fast enough that I kept using it (for the excellent TypeScript integration).

agumonkey 4y ago
Interesting, my machine was really empty so I wonder what caused it to lag that much. Maybe a strange issue on that version.

blep_ 4y ago

> file tabs going somewhere I'm going to guess this is the "preview" misfeature, where if you open a file in certain ways (e.g. by jumping into it with one of the go-to-something commands) it gets opened in a weird transient state and converted to a normal tab on edit or closed on navigating away. You can turn that off.

agumonkey 4y ago
sounds plausible indeed, i'll notify my colleague