11 ms·
Having built something similar, the biggest challenge for users is that they have to use a bespoke language, like WASP here. I suspect that it is also your bigg
by verdverm 3y ago
Having built something similar, the biggest challenge for users is that they have to use a bespoke language, like WASP here. I suspect that it is also your biggest challenge as well.
Mine is built on CUE, which at least has the potential to become a more widely used language. CUE hasn't reached sufficient maturity for broader adoption yet, so I continue to face this same problem.
https://github.com/hofstadter-io/hof https://github.com/hofstadter-io/hof
What we built is more like a framework for building WASP + boilerplate for anything, both sides of the transform in full control by the user.
I'm less bullish on the idea since LLMs that can code arrived on stage
- hot_town 3y agoWasp is as easy as learning to write JSON when you already know JS. It's more a mental barrier as new tech no one has heard of is always somewhat intimidating, whether for good reason or not.
- deleted 3y ago[deleted]
- hot_gril 3y agoI don't like DSLs because in almost every case, it would've been better as a library in a general language. You get matured primitives, control logic, and interoperability for free that way, and there are fewer surprises. But Wasp promises so much that I still want to try it. Getting auth and RPCs auto-generated would be great on its own.