A new approach to Emacs - Including TypeScript, Threading, Async I/O, and WebRender. - GitHub - emacs-ng/emacs-ng: A new approach to Emacs - Including TypeScript, Threading, Async I/O, and WebRender.
I would love to modernize the emacs core, but rewrites are usually destined to fail, more likely the older the project being rewritten is. And emacs is very old.
How about this approach. Emacs only got dynamic modules in v26, fivish years ago? All the junk compiled into the core was done so because there wasn’t something like dynamic modules. Someone (I hope I’m not signing myself up for this) should do a project to move all functionality other than the lisp engine itself and maybe some basic primitives out into dynamic modules. When the lisp engine is isolated via a stable abi, then you can redesign it without fear. Similarly with any of the modules themselves.
I would love to modernize the emacs core, but rewrites are usually destined to fail, more likely the older the project being rewritten is. And emacs is very old.
How about this approach. Emacs only got dynamic modules in v26, fivish years ago? All the junk compiled into the core was done so because there wasn’t something like dynamic modules. Someone (I hope I’m not signing myself up for this) should do a project to move all functionality other than the lisp engine itself and maybe some basic primitives out into dynamic modules. When the lisp engine is isolated via a stable abi, then you can redesign it without fear. Similarly with any of the modules themselves.
Unlikely to happen. From what I remember, even newer things (treesitter) aren’t loaded as modules but are instead compiled into the core.