> "No threading: multithreading is a hard problem, and is not well suited to a text editor:
Either we want a direct result, and we need to be synchronous with the user, so getting a 4x speed up is meaningless, we need to have an algorithm which appears instantaneous the user.
Or we want an asynchronous result, and then the processing is best left to a helper command which can be reused with other Unix tools."
I agree with them. Multithreading today in all situations is like Fuzzy logic of yesteryears. It is suppose to make everything better.
One of the big problems of editors like emacs and vim is that they haven't had means for background processing for years. And no, multithreading is not hard if you design for it. It is very hard if you need to add it as an afterthought. Some people would even say threads are easier then async.
* No NodeJS/NPM * No Electron * No multi-threading