[Faark]

Having settings is nice, but I'm not gonna spend a lot of time configuring something that I'm not yet sure will even be useful to me. Power users of / users already invested in your product will use settings to great effect, sure. But defaults matter, if you target anyone else.

Actually, you probably understand that on a deeper level. Since we are not talking about a product where "you can configure vim bindings in the settings". Its just that you personally appear to like this default and seem offended by others preferring sth else.

[usrbinbash]

The problem with defaults is, someone won't like them anyway, so trying to make them likeable to everyone, isn't going to happen, no matter how hard we try.

Using ViM as an example, using the keys that are prevalent on a US keyboard, was a sensible approach when it was developed, and since remapping the keys is probably one of the easiest things to do, it's also not an issue. In fact, writing a simple remap into a text file is easier than remapping keys in most "modern" editors, where the option to do so usually lives behind 2 sub-menus hidden behind a hamburger-button, and forcing me to scroll down an endless list that may or may not have a search function. And good luck if I want to export/import my config, or, god forbid, check it into a repo.

> But defaults matter, if you target anyone else.

Products have to target an audience and cater to them. That's how we ended up with alot of the modern webapps sharing the same usability problems, because "being like everyone else because that's what the audience is familiar with" encourages stagnancy, not evolution.

FOSS Tools on the other hand, have the freedom to explore ideas. If people don't like these ideas, they don't have to use the tools.