Kakoune is often described as a “Better Unix Citizen” http://kakoune.org/why-kakoune/why-kakoune.html#_a_better_unix_citizen meaning it tries very hard to not bundle features that can be done (better) by another program.
Good examples to illustrate this philosophy is how Kakoune relies on external windowing systems (x11, tmux, i3, kitty…) to display and organize multiple clients or how sorting stuffs is delegated to the
Today I stumbled upon on a related notion on Wikipedia, the Inner Platform Effect
The inner-platform effect is the tendency of software architects to create a system so customizable as to become a replica, and often a poor replica, of the software development platform they are using. This is generally inefficient and such systems are often considered to be examples of an anti-pattern.
In the article, web browser are mentioned as such inner-platform. One could argue that the kitchen-sink approach of emacs also follows this trend while other could counter this by stating the all-text approach and consistency sublimes the underlying platform.
With the recent inclusion of
:terminal in (neo)vim, it feels like these editors fall more and more in this trap.
To avoid the same fate to Kakoune, I hope we’ll stay vigilant about all new introduced features and after each new release introspect on design questions like Is there anything that you would remove from Kakoune? or how can we improve the glue commands by observing recurring patterns that surfaced in recent plugins.