That’s fair. Typescript has to cook with the existing js ecosystem.
Thanks, I forgot to mention but that’s what I do now. My problem with this is that I would like to make a plugin that makes sense only for me and not for the other users. I could maintain my personal fork though.
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.
We can name the chemical to make sure we don’t think about smoking it. For example, I wouldn’t say this for THC. But weed is usually smoked.
Weed can also cause cancer. In fact, it’s worse in terms of that.
When I was child I thought they are the same places, even though Austria is our neighbour country. 😄
deleted by creator
Thanks for the question. GraphQL works with multiple languages, Cuple works only with Typescript. Despite this drawback this also gives you some advantages:
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.