matijash

Yes, the main thing is that we're trying to see if AI can have an easier time using one framework vs. another, and how important it is.

All Rails-like frameworks (Django, Laravel, or Wasp in this case) claim its helpful to use something opinionated and structured, which makes sense (the tradeoff is the flexibility, of course).

We've run some early tests[1] but plan to do a more substantial benchmark next.

[1] https://wasp.sh/blog/2026/03/26/nextjs-vs-wasp-40-percent-le...

Looks neat, but I don't quite get it from the quick glance I took. What if I want to use ShadCN?

Yeah, both RedwoodJS and BlitzJS appeared at about the same time as we started Wasp (https://github.com/wasp-lang/wasp), with the same mission of being Rails/Laravel for JS.

We were excited to see that several instances of the same core idea appeared at the same time, and it gave us validation that we're on the right path. A bit sad about Redwood moving away from the original vision, but interested to see where this new direction takes it.

There is also https://wasp.sh/ (I am the creator)

Full-stack is an overloaded term, but it used to mean "a completr solution for building a web app."

From the comment above: Next.js is the opposite of a "batteries included" framework. No abstractions for ORM, background jobs, sending emails, managing attachments, web socket communication - all very basic stuff when dealing with a production application.

Ruby on Rails has an amazing DX (e.g. engines). We are trying to recreate that for JS with Wasp (https://github.com/wasp-lang/wasp)

well it's just a static code, but I guess it's software as a service still :D

Yeah, updates are not given. Often it's simply a starting point and then you're on your own. Since it's not library code, it's simply pre-written code.

Wasp is hiring a framework engineer to build Laravel for JS | Remote (US East Coast / EU)

We are Matija and Martin, founders of Wasp (https://wasp-lang.dev/) and twin brothers. We’re building a Rails/Laravel-like full-stack framework that is designed to be stack and architecture-agnostic. Currently, we’re focusing on React, Node.js and Prisma. Our secret sauce is a custom-built compiler at the heart of the framework, which “understands” how your app works across the whole stack - we’re relying a lot on code generation, and that gives us a lot of flexibility to do some pretty cool things [1] and cut down the boilerplate.

Since we launched Beta last year, we’ve seen quite strong community adoption [2] - Wasp has grown to ~14,000 stars on GitHub and is being used by indie hackers, startups, and Fortune 500 companies.

We’re currently a team of six - senior engineers (ex-Google/Palantir) + growth and a devrel. We raised our first round after graduating from YC in 2021 [3] and just recently closed another round (details will be public soon).

We are looking for a well-rounded engineer with substantial web dev experience who wants to be a part of a strong engineering/open-source culture and work on all aspects of the product with us - our custom compiler (in Haskell; but don’t worry about it [4]), frontend, backend, database/infra, deployment, CLI, ….

This is a remote position - for more details, take a look here: https://wasp-lang.notion.site/Framework-Engineer-at-Wasp-12a...

[1] https://wasp-lang.dev/blog/2024/04/25/first-framework-that-l...

[2] https://x.com/MatijaSosic/status/1839279924819145010

[3] https://techcrunch.com/2021/10/04/yc-grads-wasp-land-1-5m-se...

[4] https://wasp-lang.notion.site/Framework-Engineer-at-Wasp-12a...

Wasp (https://github.com/wasp-lang/wasp) has actually worked out quite well! It just crossed 10k stars on GitHub and is currently the fastest-growing full-stack framework for React & Node.js. It's being used in both startups and enterprises.

Although Wasp has its own DSL/compiler, the secret to its adoption is probably that it works with the existing stack, like React & Node.js. From the developer's perspective, it feels like a framework; the "compiler" part is just what gives it its superpowers.

this roughly reminds me of Xamarin? Is there a similar philosophy behind it?

Hey HN,

Wasp has been around a few times here as a full-stack framework, but one of the core reasons why we made it was to have an abstraction layer for common web app features.

Since Wasp got decently mature (Beta, 10k stars), we started investigating more on the DSL/abstraction side, and this is the first demo we built.

I'd love to hear what you think and whether you'd find it useful.

Matija

Aider is one of my favorite AI agents, especially because it can work with existing codebases. We've seen a lot of good results from folks who used it with Wasp (https://github.com/wasp-lang/wasp) - a full-stack web framework I'm working on.

A "marketingy" demo video: https://www.youtube.com/watch?v=DXunbNBpgZg&ab_channel=Wasp

This looks pretty cool! What was the hardest part about building this?

wow, that sounds like a lot! Is that your full-time job?

Thanks for this! I also like Pointer, although they have more and more sponsored stuff lately imo. Terminal trove sounds great, I like terminals a lot (who doesn't)

I feel you. Can you mention these exceptions - that's exactly what I'm interested in.

I see a Haskell project, I upvote.

Wasp team reporting to duty: https://github.com/wasp-lang/wasp

Open SaaS is still very new, but there are a couple that used the "old" version of it, which basically gave us an idea for Open SaaS. For example:

- CoverLetterGPT (https://coverlettergpt.xyz/) - generate a cover letter based on your CV and job description

- Etsy description generator (this one even got acquired): https://dev.to/wasp/from-idea-to-exit-building-and-selling-a...

No, both Open SaaS and Wasp are free and open-source, like most of the frameworks. If we manage to get the community adoption for Wasp, the next step would be to look into value-add services on top of it that can be monetized (our role models are companies like Mongo, Terraform or Databricks).

super helpful, thanks for your thoughts! Yeah, stack-agnostic is hard but not something we're opposed to. Especially if we also manage to get the community interested and involved, which is the goal with the OSS approach.

Also first time I'm hearing of the term Djangonaut, love it! :)

Thanks for sharing, Business Class looks really cool! As I mentioned in other comments, I think the situation in JS is similar to other technologies - there are a lot of oss boilerplates, but most of them don't offer the same level of polish and features as the paid alternatives. Also, a good portion of them is outdated or not actively maintained.

And that's exactly what we are going for, just with an open-source, community-driven approach.

I can imagine you had the same motivation when you created your boilerplate starter (not the oss/community thing, but above)?

That's an interesting point! What do you think would be a point when one would need to switch to Postgres?

would you mind opening a feature request? Would love to hear more about it: https://github.com/wasp-lang/open-saas/issues

Yes, exactly - Astro is used for the documentation and blog for your SaaS project

noted! If you went with vanilla JS, is there any specific library you'd use for interactivity?

Wasp is actually being developed with a vision of being stack agnostic. Currently, it's only React/Node, but we've already been playing with Python and Rust internally.

I'm not a huge podcast person, somehow always prefer a more concise blog post.

Twitter mostly! I am following a bunch of folks in indie hacker / building in public space. Also reddit

yep it was screen studio! Super handy to use