> Homogenizing expected behavior is a pretty good idea, it allows open source software to compete at a commodity level instead of a principle or fundamentals level
That applies if your only goal is to create FOSS software that competes head-on with proprietary applications, so that being FOSS is the only differentiator.
But obviously, this isn't always applicable as a general principle. If you want to enable new functionality and support new use cases, where there are a variety of approaches or trade-offs, and conventions aren't well-established yet, you probably shouldn't presumptively conform to an a priori monoculture.
> Less than pleasant because there's a pretty significant amount of overlap, but none of it is able to be homogeneous as there is some hard coding that a keymap alone doesn't allow for convergence.
This is a great counter-example, where adhering to well-established conventions for problems that are already solved is advisable. There's been a lot of divergence in UI design recently, with lots of applications moving away from decades-old standards for purely aesthetic reasons, and creating huge usability regressions in the process.