The method of install is very dodgy for linux though [1]
curl -sSL http://get.wasp-lang.dev | sh
Also the logo should be a wasp!
Dodgy install -> well true we ask you to run something, but I have seen quite a few prominent tools use this method of installation: NVM: https://github.com/nvm-sh/nvm#installing-and-updating Haskell Stack: https://docs.haskellstack.org/en/stable/README/#how-to-insta... Nextflow: https://www.nextflow.io
How would you go about it? We do plan to have packages for different distributions at some point, but unless it gets into the official repos, it is not any safer, it can still run any code and nobody checked it, am I right? Even if it was npm package, we would still have the same problem if I am correct, it can run anything? Maybe I am getting this wrong hm, I am happy to hear your suggestions!
Hm interesting question with node requirement and npm package. Long term idea is that Wasp might not have only Node backend as an option, but also other backends, and in that case it won't require Node. So that would be the main reason. Compiler itself does not need node to function, generated code needs it.
Ha the logo, we grew fond of the current one but it would be cool to also have an alternative "wasp" logo :)! Buuut if you squint and use a lot of imagination you can imagine "=}" to represent a wasp (antennae, wings and spike :D?)