Every time I've thought "here's the time for a macro" I've had this experience. Vim macros are the devil on your shoulder promising you productivity then ruining your whole day.
vscode with vim was terrible for me. I use a mediocre machine for work, and after meetings or in the afternoon it heats up. With vim in vscode, the thing could not keep up, it literally were inserting artifacts or responding with several seconds of delay after commands. I don't know if it's better, but afaik the extension has a real (neo?)vim backend that vs code talks to with each key stroke, the vim instance responds the state and vscode renders. So I don't really think it can be made better for mediocre machines
Every time I've thought "here's the time for a macro" I've had this experience. Vim macros are the devil on your shoulder promising you productivity then ruining your whole day.
Yeah multi cursors are better. In macros you mess up once and have to start over
@@justpatrick_ multi cursors are so lovely
Zig @ 50:20
0:09 this is why I can’t watch you in the living room
37:23 😂😂
vscode with vim was terrible for me. I use a mediocre machine for work, and after meetings or in the afternoon it heats up. With vim in vscode, the thing could not keep up, it literally were inserting artifacts or responding with several seconds of delay after commands.
I don't know if it's better, but afaik the extension has a real (neo?)vim backend that vs code talks to with each key stroke, the vim instance responds the state and vscode renders. So I don't really think it can be made better for mediocre machines
Let and const are still measurably slower than var. It's weird.
BLUEEEEEEEEEEEEEE
Ninja of coding😂
Use macros, be an Alpha.
Bro touch grass you seriously need to
A lexer is a trivial program. He’s touching plenty of grass. It’s honestly embarrassing that he hasn’t done it before.
Hmm true
Damn i better get my lex on