On: Neovim Plugin UI architecture

[stewbrew]

I hope this works out well for Windows users who run 20+ plugins -- no zombies or anything when neovim crashes.

[aktau → stewbrew]

I'm thinking that it won't be necessary to split out all plugins into separate processes. One could just as well use one host per scripting language and combine all plugins that use the same scripting language.

[tarruda → aktau]

Exactly, only the host process needs to implement the event loop described in the wiki.

The host can also implement custom discovery/loading of plugins in a way that makes usage of the subscribe/unsubscribe API completely transparent

[MetaCosm → tarruda]

Still, IMHO, nice to split them out -- so they don't stomp on each other or do other silly things. Same reason it is nice (but not memory efficient) that Chrome does this... individual processes are safe and sane.