So… Rust?

Its query planner is also much, much more powerful. Like it’s not even close.

There’s hardly any good reason to use MySQL today. Postgres is easier and nicer to work with, with a strong community backing it.

SQLite is completely different from both and has entirely different usecases.

Postgres, hands down. It’s far better than MySQL in every way.

Nah, neovim made too many breaking changes and prioritizes the wrong things. I’d much rather the spirit of vim continue, albeit with a better organizational structure.

Wanting them to work is reasonable, but complaining about the lack of anti-cheat makes no sense. The problem is the insistence on client-side anti-cheat to begin with.

It’s implied, because anything would behave the same.

Not that client-side anti-cheat makes any sense anyway.

File-based navigation is often inefficient anyway (symbolic navigation is much better when you can), but if you do need it, that’s what fuzzy finders are for. Blows any mouse-based navigation out of the water.

The only time a visual structure is useful is when you are actually just interested in learning how things are structured for whatever reason, but for that task, tree works just fine anyway.

You only need 1 tab to OOM if that tab is Jira. I’ve literally had tabs take up more than 10GB.

It’s not necessary. Unlike on Windows, Linux users rarely download random packages off the internet. We just use package managers.

The software itself may or may not be more secure, but acquiring software is absolutely more secure. There’s so much Windows malware people unwittingly download from the internet. Downloading from a distro’s software repository simply doesn’t have that problem.

! is supported

Vim’s command line, i.e, commands starting with :. The vanishingly few it does support are, again, only the most basic, surface-level commands (and some commands aren’t even related to their vim counterparts, like :cwindow, which doesn’t open the quick fix list since the extension doesn’t support that feature).

Your experience is out of date.

The last commit to the supported features doc was 5 years ago, so no, it isn’t. Seriously, you can’t possibly look at that doc and tell me that encompasses even 20% of vim’s features. Where’s the quick fix list? The location list? The args list? The change list? The jump list? Buffers? Vim-style window management (including vim’s tabs)? Tags? Autocommands (no, what it has does not count)? Ftplugins? ins-completion? The undo tree? Where’s :edit, :find, :read [!], and :write !? :cdo, :argdo, :bufdo, :windo?

Compared to what vim can do, it is absolutely a joke.

I’m a senior software engineer with a pretty uncommon skill set. Recruiters are the primary way that companies hire in my industry outside of networking contacts and I get contacted frequently. The job before my current one was through a recruiter.

I very much dislike Microsoft and LinkedIn in general, but not using it all is a huge handicap that isn’t worth taking on.

It’s how recruiters find me, so unfortunately I can’t. I almost never open it, though.

I use a different tool, visidata. It’s especially nice when used as a psql pager.

A text editor isn’t the right tool for editing tabular data, imo.

As for KaTeX, what I would do is have a preview process running outside of vim that watches for changes in source files and re-renders. That’s the Unix way of doing things.

There’s many very basic features of vim that VsVim does not have (like… almost all command line commands), basic features which regular vim users use all the time.

You seem to think that people using vim emulation is the norm and using vim itself is the exception and unusual… Which is very much not the case. The opposite is true, with VsVim users being a minority. It’s relatively novel among vscode users (most just use a mouse and maybe a small handful of built-in shortcuts), whereas vim itself is quite ubiquitous in the Unix world, with many Linux machines even providing it as the default editor. I know many vim and emacs users (including lots that I work with), and maybe 1 VsVim user (honestly not even sure if they do).

And I was expanding on my original comment, which was not replying to you, so there you have it.

It’s speed, but it’s also flow and a continuous stream of thought. If all your editing is being done with muscle memory and minimal thought, you can continue thinking about the problem at hand rather than interrupting your thoughts process to fumble through some context menu to make a change.

Yeah it sounds like you’re trying to mock me but it mostly just comes across as confusing. Maybe it’s just sarcasm? Hard to tell.

Anyway, it’s pretty well-known in the vim community that VSVim is pretty lackluster vim emulation. There are much better examples of vim emulation out there, such as evil for emacs.

It honestly has nothing to do with being a “power user”. It’s simply false to claim that vscode has more features than vim (which is what the parent comment was claiming), and this should be evident to anyone with more than the most basic, surface-level understanding of vim (more than vimtutor, basically). Vim is a lot more than HJKL and ciw.

I’m not annoyed with VsVim really since I honestly don’t really think about it as it’s not all that relevant. I do find it a bit irksome when people make false or misleading claims about vim from a place of ignorance about what it actually is.

It’s a strange phenomenon with vim in particular, where many people are exposed to it at their periphery, read some reductive claim about it online, and parrot said claim all over the place as though it were fact. Perhaps the nature of being a tool that most are exposed to but few actually learn.

Vim is extremely feature-rich, and people that think otherwise don’t really know how to use vim. Saying vim doesn’t have a lot of features is just a meme that isn’t true.

Also, the vim plugin for vscode is kind of a joke compared to what vim can do. It’s very “surface-level” with minor emulation of some of the common keybinds.

Okay, but it is false to claim that she is an enthusiastic supporter without an evidence of said support.