• 6 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: March 15th, 2023

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


















  • I made a home inventory management software, because I don’t have much space in my flat, so I track every single piece of the compressed pile of boxes; with qr codes on them.

    It’s a very simple app but you should have a printer to print qr codes for the boxes.

    The documentation lacks some detail, so ask anything about it, if you want to try it.

    https://github.com/fxdave/DavidHomeVentory

    EDIT: yeah I didn’t update the readme. The installation may not work. So tell me if you want to give it shot.

    It looks like this in action btw:




  • That’s my problem with this. It tries to be a desktop display server protocol without unifying all desktop requirements. Sure, X11 is old and have unnecessary things that aren’t relevant anymore, however, as someone who builds their own DE, (e.g.: tiling window managers) I see it as the end of this masterrace. Unless everybody moves to wlroots. Flameshot, for example, is already dealing with this, having at least 5 implementations only for linux, and only wlroots and x11 are standards.

    Also, imo, having windows in windows is useful when you want to use your favourite terminal in your favourite IDE. But as you said DEs can implement it simply. Let’s say wlroots will implement this but others can decide otherwise. And for those the app won’t run.

    Another example, that affects my app personally, is the ability to query which monitor is the pointer at. Wayland doesn’t care having these so I doesn’t care supporting wayland. And I"m being sad about this because X is slowly fading away so new apps will not run on my desktop.

    Moreover with X11 I could write my own hotkey daemon in my lanuage of choice, now I would have to fork the compositor.

    Do I see it wrong?



  • fxdave@lemmy.mltoLinux@lemmy.mlArch or NixOS?
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    7 months ago

    Ofc, Arch users should learn how to resolve a package conflict, or how to downgrade packages, or generally how to debug the system. Sometimes you also have to migrate config files.

    On the other hand, as an arch user, I can tell that it mostly just works. If you customize heavily an ubuntu, it will break more likely. And while you can fix an arch, you probably have to reinstall an ubuntu.

    Moreover, Arch has a testing repository which is not the default.