not very familiar with vim internals (other than knowing vim is not vi codebase), but emacs most everything is natively written in emacs lisp and has lots of ho

not very familiar with vim internals (other than knowing vim is not vi codebase), but emacs most everything is natively written in emacs lisp and has lots of hook points, emacs extensions tie into these or in some cases may carefully provide extensions/extra API's around builtin functions, etc. Helm is itself a library loaded into a given emacs image which provides useful functionality, but also that many other packages build on top of. Not sure if the point about plugins as a process was just wondering about how it works or hinting at some kind of 'workaround' for not being maintained by isolating it; issue here seems aside from potential bitrot in helm itself to be the overall ecosystem of all 'emacs helm plugins' deteriorating if helm is not maintained, which separate process plugin architecture wouldn't solve.