I thought they only banned talis

it’s a surprise, always a surprise

how many theses did Martin Luther famously nail to the door of the Castle Church in Wittenberg, sparking the Protestant Reformation?

that’d be 13, duh

refusal to allow useful endpoints that aren’t sufficiently restful

And there are good reasons for that, GraphQL-like endpoints seem great to use, but are often a bad idea. The more freedom is given through an API, the less guarantees one can deliver. Security, scalability, and maintainability all become more difficult for APIs with endpoints that attempt to do several things at once.

But most importantly, REST doesn’t tell you exactly how to build your endpoints, as long as they’re stateless, cacheable, and refer to system resources with enough context to allow their direct manipulation.

These are good principles for older and modern web apps, that hasn’t changed. In fact, one can argue that the larger and more complex the system the more important it is to simplify its endpoints. And you can build pretty complex systems while following these criteria.

I’ll let you try that one

Just the need of undoing your pants/belt already makes it easier to stand up.

And some seats have that front opening, which helps, otherwise there’s often not much room to pee sitting down.

Then there’s also some people who prefer to cover the seat with toilet paper before sitting down.

It’s easier to stand up.

You’re not everyone, OP

And what’s inherently new in modern applications? We’re transferring state and operating on resources just like we used to do. Most web apps are variations of CRUD.

I’m not saying it’s right, I’m saying the version of the story they tell themselves isn’t the same version others have.

Don’t people say that no one is the villain of their own story? They think they’re the good ones, that’s why this reasoning doesn’t work.

mr fahrenheit seems to have a drinking problem

Instead you could have a function, say t(“Ciao”) that kinda runs something like (of course loading all the translations in ram at startup and referencing that would be better than running a query for each and every string).

this backfires when the same text translates to different strings depending on the context

e.g. EN “Play” may translate to PT “Jogar” (as in play a game) or “Reproduzir” (as in play a video)

for reference, that’s usually a ISO 639-1 combined with ISO 3166-1 alpha 2

and if an exact locale match is not available, it makes more sense to return another language match than the default language fallback

you’d rather have no responses following a standard rather than only some doing that? No, thanks.

it forces a login just to browse it - I hope it’s unintentional

you must find it really annoying to learn Spanish, German, Portuguese, Italian, and a bunch of other languages that have gendered nouns.

or “oh yup, just need to give it a kick”

i would hate it if someone shat in my cupboard

used OpenSearch in a recent project, but the number of annoyances with it are through the roof. From SSL certs setup to bad defaults in settings, and the fact it does type inference for indices requiring you to manually recreate the index, and the docker container that takes 30s to start every time…

If you can use mongo, just use that. Or pick something other than OpenSearch if that’s overkill for you.