[verdverm]

I think a lot of people have tried to "low code" this problem. The issue is that everyone has their preferred tech stack and low-code typically only has one choice. Using a DSL for logic (conditionals in yaml strings), or a bespoke language (like DarkLang or WaspLang), is a difficult sell. Developers want to use their language of choice with real programming constructs.

The most interesting approach, the sort of holy grail if you will, is to write your code as a single application, and then the system figures out how to distribute it if/when needed. ServiceWeaver is this concept in Go

https://serviceweaver.dev/

Reddit "critiquing" ServiceWeaver: https://www.reddit.com/r/programming/comments/1962avu/a_goog...

[matijash]

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.

[verdverm]

You work for Wasp, so we'll take it with a grain of salt.

I have never seen Wasp used in the wild, because of the aforementioned limitations

- bespoke language

- stack chosen for you

What Wasp provides would be better addressed as a library.

Also, NextJS is the fastest growing, fullstack framework for React, largely because of the superior DX

---

an example of where Wasp has bad DX / DSL edge cases

> {=psl psl=} tags for database schema

You're weaving multiple DSLs together, which compounds the problem.

https://wasp-lang.dev/docs/tutorial/entities