• 1 Post
  • 7 Comments
Joined 1 year ago
cake
Cake day: March 15th, 2023

help-circle
  • I liked this discussion. However, I think both of you have different axioms. It’s a pro-socialism vs pro-capitalism debate.

    In capitalism, we need innovation to create new value. Or you can pollute water to sell water bottles which will have value now. It’s up to citizens to decide what to restrict that was publicly available or what to innovate.

    In socialism, the innovation is only happening where it needs to happen carefully planned and funded by the government.

    I’m rather socialist, so I’d defend it:

    Having a software with inability to modify is injustice, It’s the same as polluting a water to sell it. Even if we need to pollute the water to sell it, it doesn’t justify pollution.



  • 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.