That’s fair. Typescript has to cook with the existing js ecosystem.
there won’t be two pointers, but multiple devices are supported
I would imagine it as lemmy. It would be a free, ethical software which is indirectly funded by the government. Everybody uses facebook so that’s a good reason to turn it into a public property. We could make it without anti-features. Made for people, not for profit.
I would prefer paying for it with my taxes. Not for facebook though.
I bought pads as well but the original ones didn’t break. I wanted to replace them with my new one, however i found the new one is more stiff while the original is soft that components can sink into it. I didn’t know that it’s a thing. So i kept the original. (If anybody is interested there were 0.5mm and 1mm pads on the cooler.)
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.
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.