<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kinos</author><text>The only thing preventing me from jumping right onto this is the fact it doesn&amp;#x27;t seem to be an oauth2 provider, and it doesn&amp;#x27;t seem to have the verify&amp;#x2F;reset&amp;#x2F;etc jobs necessary for username &amp;amp; password.&lt;p&gt;Verify&amp;#x2F;reset&amp;#x2F;etc is always what pushes me away from doing multi-user webapps. Its a headache every time due to needing to think about e-mail, and I&amp;#x27;d love an all-in-one oauth2 provider with signup and etc thats super lightweight and just does everything through an API.</text><parent_chain></parent_chain></comment><story><title>Show HN: Wasp – DSL/framework for building full-stack web apps – now in beta</title><text>Hey HN! Wasp (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;&lt;/a&gt;) is a simple config language (DSL) and framework for building full-stack web apps. You describe the high-level features you want (auth, CRUD, async jobs, …) using the Wasp DSL, and write the rest of your logic in React, Node.js, and Prisma. We’re focused on simplifying developer experience and ensuring best practices. Everything is open source.&lt;p&gt;Why another full-stack framework? And why a config language&amp;#x2F;DSL? We were still experiencing a lot of boilerplate (repetitive tasks) using other frameworks—things like duplicating data models across database&amp;#x2F;server&amp;#x2F;client, implementing CRUD API, setting up auth, and choosing and stitching together all parts of the stack.&lt;p&gt;There are two main reasons for the DSL approach - 1) short-term: simpler and cleaner DX via a declarative language that helps avoid boilerplate, and 2) longer-tem: laying foundation for the stack &amp;amp; architecture independent system.&lt;p&gt;Since Wasp analyses the app’s requirements in compile time, it can decide how to generate the target code (React &amp;amp; Node.js currently). In the future it could support other stacks such as e.g. Vue&amp;#x2F;Svelte on the client and Python&amp;#x2F;Go on the server, even allowing for mixing’n’matching. The same goes for the architecture (dedicated server, serverless, …).&lt;p&gt;Our big vision for Wasp is to become a stable, stack-agnostic language for describing (web) app requirements (like SQL for databases or Terraform for infra) that interops with the existing stack. Wasp-lang stands for “Web Application SPecification language”.&lt;p&gt;Besides the DSL, another valid approach would be to offer an SDK in e.g. JS or Python to build Wasp AST (like Terraform and Pulumi now both offer). We see it as another “frontend” for constructing the AST and might also introduce it in the future.&lt;p&gt;Under the hood, everything is compiled to a client (React) and server (Node.js&amp;#x2F;Prisma) apps and we generate static files and a Docker image you can use for deploying to your platform of choice.&lt;p&gt;Wasp had an Alpha launch 1.5 years ago (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=26091956&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=26091956&lt;/a&gt;). Now we are more stable and feature-full. We still expect things to change, so wouldn’t recommend using Wasp for heavy production or mission-critical systems just yet. But it has been used for hackathons, internal tools and even revenue-generating products (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;26&amp;#x2F;erlis-amicus-usecase&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;26&amp;#x2F;erlis-amicus-usecase&lt;/a&gt;).&lt;p&gt;The current release is our biggest since we launched (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;wasp-beta&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;wasp-beta&lt;/a&gt;). Besides general stability and DX improvements, it brings support for TypeScript (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;typescript-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;typescript-feature-ann...&lt;/a&gt;), Tailwind (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;16&amp;#x2F;tailwind-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;16&amp;#x2F;tailwind-feature-annou...&lt;/a&gt;), async jobs via pg-boss (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;06&amp;#x2F;15&amp;#x2F;jobs-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;06&amp;#x2F;15&amp;#x2F;jobs-feature-announcem...&lt;/a&gt;), full-stack authentication (now also with Google) (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;localhost:3000&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;15&amp;#x2F;auth-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;localhost:3000&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;15&amp;#x2F;auth-feature-announcem...&lt;/a&gt;), and by popular demand, Wasp LSP with VS Code integration (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;12&amp;#x2F;01&amp;#x2F;beta-ide-improvements&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;12&amp;#x2F;01&amp;#x2F;beta-ide-improvements&lt;/a&gt;).&lt;p&gt;Our next focus will be on making Wasp even easier to use (examples, starter templates, UI helpers), and we’ll look into tighter weaving of data models with the rest of the stack and expanding the DSL with more functionalities.&lt;p&gt;We’re around to answer questions and look forward to hearing everything and anything you have to say!</text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dom96</author><text>Congrats on this new milestone! I had a lot of fun completing some Hacktoberfest tasks back in October for Wasp, it was a lovely experience.&lt;p&gt;What&amp;#x27;s most interesting (to me at least, as someone that loves building and learning about new languages) is that Wasp is YC funded. Probably the first language project I have seen to be part of YC.</text><parent_chain></parent_chain></comment><story><title>Show HN: Wasp – DSL/framework for building full-stack web apps – now in beta</title><text>Hey HN! Wasp (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;&lt;/a&gt;) is a simple config language (DSL) and framework for building full-stack web apps. You describe the high-level features you want (auth, CRUD, async jobs, …) using the Wasp DSL, and write the rest of your logic in React, Node.js, and Prisma. We’re focused on simplifying developer experience and ensuring best practices. Everything is open source.&lt;p&gt;Why another full-stack framework? And why a config language&amp;#x2F;DSL? We were still experiencing a lot of boilerplate (repetitive tasks) using other frameworks—things like duplicating data models across database&amp;#x2F;server&amp;#x2F;client, implementing CRUD API, setting up auth, and choosing and stitching together all parts of the stack.&lt;p&gt;There are two main reasons for the DSL approach - 1) short-term: simpler and cleaner DX via a declarative language that helps avoid boilerplate, and 2) longer-tem: laying foundation for the stack &amp;amp; architecture independent system.&lt;p&gt;Since Wasp analyses the app’s requirements in compile time, it can decide how to generate the target code (React &amp;amp; Node.js currently). In the future it could support other stacks such as e.g. Vue&amp;#x2F;Svelte on the client and Python&amp;#x2F;Go on the server, even allowing for mixing’n’matching. The same goes for the architecture (dedicated server, serverless, …).&lt;p&gt;Our big vision for Wasp is to become a stable, stack-agnostic language for describing (web) app requirements (like SQL for databases or Terraform for infra) that interops with the existing stack. Wasp-lang stands for “Web Application SPecification language”.&lt;p&gt;Besides the DSL, another valid approach would be to offer an SDK in e.g. JS or Python to build Wasp AST (like Terraform and Pulumi now both offer). We see it as another “frontend” for constructing the AST and might also introduce it in the future.&lt;p&gt;Under the hood, everything is compiled to a client (React) and server (Node.js&amp;#x2F;Prisma) apps and we generate static files and a Docker image you can use for deploying to your platform of choice.&lt;p&gt;Wasp had an Alpha launch 1.5 years ago (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=26091956&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=26091956&lt;/a&gt;). Now we are more stable and feature-full. We still expect things to change, so wouldn’t recommend using Wasp for heavy production or mission-critical systems just yet. But it has been used for hackathons, internal tools and even revenue-generating products (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;26&amp;#x2F;erlis-amicus-usecase&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;26&amp;#x2F;erlis-amicus-usecase&lt;/a&gt;).&lt;p&gt;The current release is our biggest since we launched (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;wasp-beta&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;wasp-beta&lt;/a&gt;). Besides general stability and DX improvements, it brings support for TypeScript (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;typescript-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;29&amp;#x2F;typescript-feature-ann...&lt;/a&gt;), Tailwind (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;16&amp;#x2F;tailwind-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;16&amp;#x2F;tailwind-feature-annou...&lt;/a&gt;), async jobs via pg-boss (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;06&amp;#x2F;15&amp;#x2F;jobs-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;06&amp;#x2F;15&amp;#x2F;jobs-feature-announcem...&lt;/a&gt;), full-stack authentication (now also with Google) (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;localhost:3000&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;15&amp;#x2F;auth-feature-announcement&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;localhost:3000&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;11&amp;#x2F;15&amp;#x2F;auth-feature-announcem...&lt;/a&gt;), and by popular demand, Wasp LSP with VS Code integration (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;12&amp;#x2F;01&amp;#x2F;beta-ide-improvements&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wasp-lang.dev&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;12&amp;#x2F;01&amp;#x2F;beta-ide-improvements&lt;/a&gt;).&lt;p&gt;Our next focus will be on making Wasp even easier to use (examples, starter templates, UI helpers), and we’ll look into tighter weaving of data models with the rest of the stack and expanding the DSL with more functionalities.&lt;p&gt;We’re around to answer questions and look forward to hearing everything and anything you have to say!</text></story>