I thought originally it may have been an OSS extension, but it actually seems to have been a proprietary project licensed under the Microsoft Software License, similar to Copilot and such.

I've use eclipse many times in the past, and hated every second of it. Stupid defaults, very stupid defaults.

I also don't like visual studio, the way it forces me to work with "solutions", like i can't have two different projects open at the same time.

Netbeans instead, that always felt so natural to me. And MPLABX is of course the one i use most of the time (like 60%, then 10% VSCode and 20% Qt)

I also really like Qt Creator, for generic C++ development too. And i would probably feel at home with KDevelop

That's when you know you want to create a keybinding, here's a suggestion that opens a split below the current window with 10% height and starts a terminal: `nnoremap <leader>ft :belowright 10 split | terminal<CR>`

But is a terminal really what you want or do you just want to run a command? Maybe just `:!command` is enough 9/10 times that you reach for <leader>ft? In that case a common binding is `nnoremap ! :!` which puts you in that mode with a single key.

> get used to using macros as a replacement for multicursor

This exact example was how I realized the vim way is better than my assumptions. I used to install a multicursor plugin and bind to Ctrl+d because that's what I knew. When I learned macros and s/old/new it became irrelevant.

You seem to already know a lot of the possibilities that you can learn, I didn't and discoverability in vim isn't great. So I just forced myself to search for whatever I didn't know how to achieve and many times ended up learning something extremely powerful.

Today I have all sorts of useful little functions, <leader>m is make, or gcc if no Makefile exists. And now I've extended it to generate mermaid charts in markdown files and open them in my imageviewer and so on.

That's the true power of vim to me, adding standard tools from the system in keybindings and just getting it to do things MY WAY, not how I was taught it should work. It follows the unix philosophy and batteries included is by definition not part of that mentality.

Am I right to understand that as people don't upgrade their hardware, they're safe from that, right? Sounds like a plus to me.

I'm not judging your for it, but to me that sounds like learning the violin by plucking the strings like a guitar. You're increasing the learning period by following old habits which may even be harmful.

I think it's better to just use the new editor sparingly, learning what you need, then switch fully once you're comfortable. A filetree is never necessary unless you're actually exploring and a file manager would be better for that. Vim has global search with `grep` and the terminal is available through `ctrl-z` and the `:terminal` command.

I've seen people touting Neovim setup that are just making things complex and fragile for no reason.

If you've only ever used this type of debugging, you should really try out a real IDE debugger once. The difference in productivity when you can use your IDE to navigate to, say, the usages of a function and then just press a keyboard shortcut to put a breakpoint on the line with that usage is immense.

Compare this to the native debug support: you have to leave the interactive debugger, move to your editor, find usages, note down the file name and line number, then go back to your interactive debugger and type a manual break command (break my_file.rb:2517 or something). All of that context switching and remembering is replaced by a single keyboard shortcut in Emacs, VS Code, or any other integrated debugger. And no, adding manual breakpoints in your source code is not simpler - what I'm describing works interactively while your code is already running, whereas a breakpoint statement requires you to restart the whole process.

I do not even need that. Modal editing is enough to keep me away from all the VI clones. I hate it with a passion.

I have a fully customized Emacs that I use for anything Lispy and it's great for that purpose but everything else is just "ok".

I try to use Zed but since it is a commercial offering it is just a matter of time until it gets entshitified too.

Vscode is/was really good but it seems to get worse and it's Microsoft.... I run out of editors it seems.

They make this beautiful pasture (Windows XP wallpaper) and then lay mines all over the field. Put up signs that say “Free Lemonade” and charge for parking.

They got a storm of criticism after that announcement, but Microsoft seemingly has not given a single fuck about that and has not backtracked on this decision.

(Just like they technically could have allowed Windows 11 to run on older PCs with some disabled features out of the box, but didn't)

First: Vim comes from vi, which is a visual mode for ex, which is a supercharged version of ed, which is (the standard editor) a line editor. With ed, you don't really write, you issue commands that does things to the file. Think of the file as a long roll of paper and the program as an assistant. So a command could be "replace your on line 14 with you're" or "delete line 34 to 45". Ex added more commands, Vi made it interactive, and Vim added even more features (syntax highlighting, scripting, location list,...). But still the same mode of interaction remains. The cursor is what you control. It's not just an indicator where the next character will appear or be deleted. It's the starting point of more powerful interactions.

Second. You're not supposed to move the cursor that much in insert mode. For 3 characters to the left, I just backspace and rewrite. For more, I go to normal mode and use F, f, T, or t which will land me to the character I want. Then I can use something like x (delete character) or r (replace character) without having to enter insert mode. There's a lot of movement beside hjkl, and I rarely uses h or l for things that further away than two characters.

Third. There's not a lot of key on the keyboard. $ is end of line in most regex dialect, ^ is beginning of line which would be actually the first character, but most people would assume it's the first non-whitespace character, so that's how they went. In C, curly braces mark blocks of code, so it's a small leap to use it for blocks of text, aka paragraphs.

Fourth. My mnemonics are f (find) and t (to). The latter does not include the character.

Firth. A lot of people remaps the caps lock to either Ctrl or ESC.

Sixth. They're different computers so there's no shared clipboard. Sharing information between the clipboard can be done using escape sequences, but I've never bother to. I just maximize the current buffer so I can use the terminal selection. And if I wanted more than a screen (dmesg), I'd pipe the command to a file and then download that file with sftp.

Seventh. Jetbrains only have debuggers for a handful of programming languages while `printf` is universal. And there's no law forbidding installing an IDE alongside your editor.

There's a ton of historical baggage there. Thankfully, a bit of it can be resolved by setting esc and/or ctrl in caps lock.

Because no one on the kernel team likes deleting code, specifically because someone will try to install it on their old ass work laptop from a decade ago.

Microsoft choosing not to support that old ass laptop is a company choice. There are costs involved with maintaining the support structure. Whereas Linux is primarily funded by enterprises who use it on servers, which may not be updated hardware wise in a longer period of time.

If Linus Torvalds or Miguel De Icaza introduce copilot, I swear I’m going to go all in on BSD.