News for hackers. Stuff that matters.

A comment on Back end where you just define schema, access policy, and functions. Parent comment

Re:Back end where you just define schema, access policy, and... by emilss on Sunday February 22, 2026 @07:22PM (#47116398)
True, I'd hate learning a new DSL...

Also true, suppose one would have to basically make it support basically full nodejs code? I wonder how restricting AWS Lambda gets, once you start building something complex.

Why instead of AI? I started thinking about this more because of AI, if you have a clear definition of your backend, with solid primitives, that can just get deployed at each commit, without much concern for the infra and such, this makes it easier to slop your way through features?

[ Parent | on HN ]
Re:Back end where you just define schema, access policy, and... by verdverm on Sunday February 22, 2026 @07:57PM (#47116671)
Not if I have to load up a bunch of explanation and pollute my context because of a tool with bespoke DSL

I already built this same thing with CUE as the DSL. So (1) my questions come from experience (2) the LLMs already know CUE because it has been around longer and it's in their training data

[ Parent | on HN ]