You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a long break, I want to revisit emacs-ng js side. Over time, it appears that the JS feature set has fallen into decay. I see that @declantsien appears to have commented it out for now.
Instead of the tightly coupled JS engine, the JS engine will run on a separate thread. Deno and emacs-ng will communicate via message passing. This may slightly break compatibility with older JS packages - however I generally think I can keep general compatibility.
The text was updated successfully, but these errors were encountered:
After a long break, I want to revisit emacs-ng js side. Over time, it appears that the JS feature set has fallen into decay. I see that @declantsien appears to have commented it out for now.
I would like to take that as an opportunity to clean up the JS side of things using some lessons learned from https://github.com/DavidDeSimone/ng-js.
Instead of the tightly coupled JS engine, the JS engine will run on a separate thread. Deno and emacs-ng will communicate via message passing. This may slightly break compatibility with older JS packages - however I generally think I can keep general compatibility.
The text was updated successfully, but these errors were encountered: