expr

It's not as big of a deal as you might think. You still have a lot of your muscle memory from regular keyboards. It might take a little while to adjust when switching between the two, but it's not that bad.

If you switch between the two enough, you can actually type on both equally well.

A lot of mechanical keyboards these days are programmable using QMK Firmware. I actually use https://www.caniusevia.com/ instead though, which uses (a subset of) QMK under the hood but allows programming the keyboard via a Web app on the fly.

For my layout, I have the standard QWERTY layout for the unmodified layer (layer 0, holding no keys). Then I can hold down a thumb key for switching to a different layer, which has things like symbols, F1-F12, Home, End, etc. The layout I use isn't too far off the default Iris layout, just a few tweaks here and there (like one that allows me to hold a key for control, or tap that key for escape).

Vim has an entire dedicated scripting language built right into the editor and accessible while editing.

Even without plugins, sometimes certain things can be too slow and you want to stop them.

Ctrl-C absolutely should not exit. There's plenty of times you want it in vim to interrupt something in the editor.

As others have said, it's on the screen if you open vim without a file. Otherwise, it's a tool for people that bother to learn how to use it. As someone who has been using it daily for the last 10 years, I would find it incredibly obnoxious to have a bunch of useless screen clutter telling me basic things that are easily learned.

It's simply muscle memory. You think of the action and your fingers do it faster than you can consciously think of where they need to go. But I also use a split ergonomic keyboard (the Iris) and have symbols accessible from home row behind a layer. Though I can switch to a standard keyboard as needed too.

Been using it for all of my software development for the last 10 years. It's fantastic.

That's what happens when you start using LLMs for all of your software development. Garbage code all day long.

Because they vibe code the shit out of everything now. Insane shit is bound to happen.

Oh for sure, it's definitely less common, though there are a number of other companies running it in production as well. This isn't my first Haskell job, after all. My last job was also a similar size company and codebase. Facebook was even running it for a while for their sizeable abusive content detection system before that was shuttered due to company politics/policies (back when they were trying to do something about it at all).

But yeah, it's not the first pick for a lot of companies, though I tend to think of that as a simple mindshare/inertia explanation than anything inherent to the language/ecosystem.

I'm not entirely sure what the Haskell comment is supposed to mean. Just that it would be cool? Or that it would be hard?

Because if it's the latter, that's just really not true. Haskell's quite well-suited to writing web servers and has many high-quality libraries for it. I'd actually argue that it's one of the best options for it in 2025. I write Haskell professionally developing web servers we use for our web and mobile apps. We have about 0.5 million lines of Haskell in production (and given how terse Haskell is, you could expect that size to be at least double were it written in an imperative language).

Nothing about this usage is reasonable. It is detrimental in every conceivable way: https://arxiv.org/abs/2506.08872.

That's what I do, but I really wish I could tell them to fuck off with that shit.