> I wish every application worth putting a plugin system in it followed this philosophy.
Does it open the door for compromising on the core XP whilst expecting everything to be a plugin for example? It's also making the task of testing N^2 complex.
Sometimes a well-thought-through plugin system is no plugin system.
Kakoune (https://github.com/mawww/kakoune) is a good example of it.
I know it's an Emacs celebration party, but that one decision made Kakoune super
stable and nice to use.
(I'm looking at you NeoVim).
>Does it open the door for compromising on the core XP
in some applications yes, in Emacs I'd say no because Emacs itself is extensible and let's people utilize its own core functions and is itself almost like a mini OS. For example the completion framework is enhanced rather than replaced by plugins like Consult.
There's a systems thinking aspect to Emacs plugin development. People make plugins always with Emacs itself in mind and to improve Emacs rather than merely the plugin. It's very anti-Unix philosophy in that way. Org-mode or Magit are good examples of this, they work well, and really only well, within Emacs.
It's what I've struggled with every time I tried out NeoVim where I ended up with ten plugins all loosely held together by tape and always something broke when something else was updated.
Does it open the door for compromising on the core XP whilst expecting everything to be a plugin for example? It's also making the task of testing N^2 complex.
Sometimes a well-thought-through plugin system is no plugin system. Kakoune (https://github.com/mawww/kakoune) is a good example of it.
I know it's an Emacs celebration party, but that one decision made Kakoune super stable and nice to use. (I'm looking at you NeoVim).