New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the extend of depending on javascript? #140
Comments
Users can use binaries (executable), see install with binary, JavaScript isn't required. But you do need to install node for Eask development.
I recently had a discussion with Eldev is the tool that doesn't rely on any of these (Python or Node), here are my thoughts:
I know this tool but does it has some bug? I don't remember where I got the information, but like I mentioned above, I would like to avoid all the hassles. 😅 LMKWYT? ;) |
To me it makes sense. I haven't tried the binary install method. I guess the startup time might be a bit of a pickle to solve with pure elisp indeed. |
There is currently one issue with binary, see #104. Basically, you cannot use: $ eask run another-eask-command In Eask-file: (script "another-eask-command" "eask info") ; ❌ This wouldn't work with binary, but running from node is good.
(script "test" "echo Hello!") ; ✔️ Good! |
I love Eask and the UX it provides and I wish it would get bigger adoption. I think one issue with that would be the javascript dependency.
Many people using Emacs do not use javascript and don't know how to install node (it's a bit of pain). Cask was using python which is almost on every computer and even that was a problem. Eventually, they got rid of the python dependency and it's now pure elisp.
I see that a lot of the javascript is used for parsing (yargs). If, hypothetically, we port yargs to elisp, would that be a lot more code left in JS?
There is https://github.com/rejeep/commander.el but it's very basic compared to yargs. We could either take it and improve it or start something from scratch.
Here's a little table of tools I've found in the space of package dev/management. All of them seem to be pretty dead except the first three.
The text was updated successfully, but these errors were encountered: