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

help-circle


  • By the way, I am an apple hater because I tried apple after years of using Linux and it was a true mess. Here’s a story: I had to make an app building CICD pipeline and guess what? We had to run a macbook as a server because they fucking cannot share at least a VM for building. A CLI command brought up a GUI confirmation. How should I automate something that brings up a GUI. Garbage. Package management is horrible. Command line utilities was outdated. Case insensitive filesystem. Then Ruby…

    And it’s not enough that they are shit, but they are actively holding back innovation. They held back PWAs for example. And they shit on open-source. They are the definition of vendor lock-in.

    They look good though.



  • fxdave@lemmy.mltoApple@lemmy.world*Permanently Deleted*
    link
    fedilink
    arrow-up
    15
    arrow-down
    30
    ·
    6 months ago

    Vertical integration and progressive company are good for Apple but for the consumer they are irrelevant I think.

    Security is ok, privacy must be a joke, siri is listening, just like google. You have to be logged in to install an app from the store etc…

    Pretty limited ui. Some might like it, some may don’t, but they can’t change nothing.



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