Seems like a lot of supportive commenters didn’t try CSS-IN-JS like @emotion/styled, stitches, styled-components. Where are you guys? Why learning alternative names for CSS rules considered to be better, than just using those good ol’ "let you do everything what you want"s.

aah my favorite template engine, I have seen it so long ago

Thanks for the question. GraphQL works with multiple languages, Cuple works only with Typescript. Despite this drawback this also gives you some advantages:

• The Request and Response types are auto-inferred from the endpoint you write
• Because the types are in Typescript you don’t need to generate a client, you just simply use it with @cuple/client and get instant feedback.
• You don’t have to learn another language. It’s just typescript.

Practically it means less boilerplate and it let’s you focus on the feature you write. Cuple is also not a query language, you get what the server sends you, it’s more likely a type-safe FFI binding. With Cuple you can build a REST API, or anything similar to that with HTTP method, header, path, query, body, and you can use it type-safely.

That’s fair. Typescript has to cook with the existing js ecosystem.

deleted by creator

I see, thanks

Honestly, I don’t get it.

Is it about the syntax sugar? Would you like to use callbacks instead?

Async programming is when you achive concurrency even with one thread. It’s needed. There’s no alternative to this.