I don’t recommend GL.inet routers. I have the Marble and it is slower than my ISPs router. It has a thing called network hardware acceleration, and it breaks my home server. Services just stop working well with it. So I keep it turned off. When I reported the issue they said it is working for them and came up with a completely hypotical setup…

With AdGuard enabled it frequently froze and I had to reboot it. For some reason even without AdGuard name resolution is noticeably slower. Doesn’t matter if I use my ISP’s DNS or not.

Also, DynDNS doesn’t support custom names, so I installed an alternative service for mywire.org.

Overally, this box came with drawbacks, but no doubt about it is hackable in the good way.

I would like to try openwrt’s own router, next time.

Shit, I thought this is an anti-marxist meme then I read the community. It’s good to see lemmy gaining popularity. :'D

afaik from youtube, HDL is good, LDL is bad.

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.