3 ms·

Present a C-API so that you could write extensions in any language assuming someone wrote bindings.

• Buttons840 5y ago
  What happens when I start such an editor? It starts the basic editor and then it spins up 15 other language environments / interpreters to run the extensions?
  • tomcatfish 5y ago
    If that's what all your usecase's developers think is best, sure.
  • samus 5y ago
    Yeah, why not? If implemented correctly, this should ensure that the user interface is always snappy because all the slow parts (language servers, build systems, search, embedded applications) would be in backends. Modern multi-core systems are especially well-suited to such an architecture. The biggest issue would be fragmentation of the extension ecosystem. The ecosystem would be split along implementation languages, which is an altogether disadvantegeous dimension.