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?)
Re:Show HN: Wasp (Alpha) is out – DSL for building web apps ...
by matijash on Wednesday November 11, 2020 @10:25AM
(#25059090)
Hi HN! Together with my brother I've been developing Wasp - a language for building web apps with as little boilerplate as possible. It is open-source and integrates with React/Node.js/Prisma. We just released Alpha and are looking for testers and contributors.
Re:Show HN: Wasp (Alpha) is out – DSL for building web apps ...
by matijash on Wednesday November 11, 2020 @11:22AM
(#25059628)
Thanks a lot for your support! We are ourselves not yet sure in which direction will Wasp evolve but find it very exciting to work on it, especially when we see other people being excited about it too :)
Re:Show HN: Wasp (Alpha) is out – DSL for building web apps ...
by matijash on Wednesday November 11, 2020 @11:18AM
(#25059585)
Thanks for giving Wasp a spin! Yes, we put a lot of effort in the generated code to look "human" - it is not perfect and we had to make some compromises for now to move faster, but it is something that is high on our list of the priorities.
Hope we'll be able to put even more resources in that, once we flesh out the basic features.
The method of install is very dodgy for linux though [1]
It seems to require nodejs, so why is this not an npm package?Also the logo should be a wasp!
[1] https://curlpipesh.tumblr.com/
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?)
Thanks for any feedback and comments!
I hope projects like this get some traction and prove that we can move higher level than where we are atm with the frontend/frontend-backend code.
I also like that you can edit the wasp file and the app regenerates live in the local environment, feels super fluid