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.
Is this still being developed? I remember there was some excitement with it early on but haven’t heard much since. Looking at the readme, it seems a bunch of its features (and value adds) are no longer maintained or just straight up don’t work anymore. Seems like there just weren’t enough javascript developers interested in Emacs to help this project continue.
I think the excitement was from an other (now defunct) project called REmacs, one of it’s main goals was replacing the C Core with Rust. Emacs Lisp is old and has its problems, but I prefer it over JS/TS as extending language for Emacs.
I recently had cause to try to load some code into a JavaScript repl from a typescript project. Man what a nightmare.
The js ecosystem is very difficult to work with. Many options and browser issues are intertwined. Clever ideas abound… but that might be part of the issue.
JavaScript wouldn’t be an improvement over elisp imo. The theory is that a more accessible language would bring users, but many devs aren’t interested in anything but getting the job done with vs code and then going home.
And honestly the ridiculous quickness in which things get deprecated despite no replacement is a bad developer mindset.
Is this still being developed? I remember there was some excitement with it early on but haven’t heard much since. Looking at the readme, it seems a bunch of its features (and value adds) are no longer maintained or just straight up don’t work anymore. Seems like there just weren’t enough javascript developers interested in Emacs to help this project continue.
I think the excitement was from an other (now defunct) project called REmacs, one of it’s main goals was replacing the C Core with Rust. Emacs Lisp is old and has its problems, but I prefer it over JS/TS as extending language for Emacs.
I recently had cause to try to load some code into a JavaScript repl from a typescript project. Man what a nightmare.
The js ecosystem is very difficult to work with. Many options and browser issues are intertwined. Clever ideas abound… but that might be part of the issue.
JavaScript wouldn’t be an improvement over elisp imo. The theory is that a more accessible language would bring users, but many devs aren’t interested in anything but getting the job done with vs code and then going home.
And honestly the ridiculous quickness in which things get deprecated despite no replacement is a bad developer mindset.
Out of curiosity I installed the .debs. They appear to have been empty as a ‘dpkg -L’ only shows two directories under /usr/local.
I see recent commits but it appears as though the builds are broken at the least.