> ...understand the web app’s requirements during the build time and reason about it before generating the final code. For example... it could pick the most appropriate architecture based on its understanding of the web app and deploy it to serverless or another type of architecture.

Wowzer! For me, this is the main benefit. I'm a big believer in low-code platforms like darklang, because the fundamental truth that bugs are a function of both SLoC and underlying infrastructure is never going to change, and one solution to that is to automate as much of it as possible.

The only problem I see is that these automations that eliminate code and abstract away the infrastructure often result in a new class of harder-to-debug or worse never-seen-before bugs. And so, building a language that "solves software engineering" may require a lot of patience and perseverance. With that in mind, how long do you plan to keep at it? How long term are you thinking you'd be doing this? I mean, you could still be working on wasp-lang whilst working full-time elsewhere... but then, that requires a different level of commitment when the business around it has failed.

> Wasp’s compiler is built in Haskell

Two questions, if I may: Why Haskell? Did you also consider OCaml (à la Rust) at some point?

Edit: I see wasp-lang is MIT licensed. Why not Apache v2 (or even MPL v2)? Especially since MIT lacks patent-grants clause.

Excited to see how wasp-lang evolves. Thanks!