The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.
For anything claiming to be RESTful, it’s a crime.
The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.
For anything claiming to be RESTful, it’s a crime.
The article is talking about art in promo material.
Think about it: whenever you see a piece of production art featured in a social media post or a press release or a game announcement at a big televised showcase, all you ever see is the art. You never know who made it, whether it was created by an individual or a small team (or even a studio).
(another pet peeve of mine is “rest” APIs that use 200 response codes for everything)
Yup, also some APIs use GET for everything. It’s a pain. And it means that filtering by verb only helps if you’re intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you’re developing the API yourself.
I misread the first one as “Dipshit” at first 🤣
Heroic Game Launcher is pretty cool. It does game save sync with GOG games too.
I think part of the issue is how business accounting practices work. When you buy a machine, you can call it a capital investment and count its value as an asset. When you hire a person and cultivate them for years, from an accounting perspective their salary is strictly a liability / expense. Even though that person is an asset in every other way, our standard accounting practices don’t reflect that.
I started using restic for backups.
Pro:
Con:
Anything Zigbee or Z-Wave.
A third option is KeePassXC. You can set TOTP seeds for entries there.
Get a second opinion. You could probably get a single implant to replace the broken molar.