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.
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.
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
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
context, for the unaware
https://en.wikipedia.org/wiki/1995_Greater_Pittsburgh_bank_robberies
you’d rather have no responses following a standard rather than only some doing that? No, thanks.
returning a 400 never prevented me from adding more info to the response
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”
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.
what do you mean removes side loaded apps?
that’d be useful to know last week for me…
not only that, but people are just saying they’ll give it money and never doing, so it’s a costless bribe. Everybody benefits!
That’s my point, checking a few boxes in the settings is the bare minimum if you care about it, so idk what’s the value in comparing defaults.
And privacy is often a tradeoff, if a browser doesn’t have the strictest by default, it’s probably because the ones who forked it didn’t consider it a good tradeoff.
That only seems relevant if one uses the defaults, and if you care about privacy you probably don’t, so idk what’s the goal of this little experiment other than just curiosity.
It’d be a whole lot more useful if it was “here’s the connections these browsers made after enabling all privacy-preserving settings they offer”.
I’ll fix it in an hour. When I get to it in a couple of weeks.
These dinosaurs are used to cable tv, where the ratio of ads and mediocre content is 50/50. If anything, they think there should be more ads.
“The marketplace is really challenged with too many players in the market,” Zaslav said. “When people turn on — the consumers put on their TV, it’s a terrible consumer experience. In almost every market in the world, there’s just way too many choices. And you’re googling, ‘Where is it? How do I get from one to the other? How do I get into that platform?’”
lol the problem is on their faces and they can’t see it.
Too many choices is not a problem, just like a monopoly is not a solution. Exclusivity deals are the problem. If most content was cross platform, this wouldn’t be so awful like it is today.
They’re reaping what they sowed.
backed by thoughts and prayers, like a good christian currency
in god we trust
heh, if it was in the show he’d be arrested for shoving the hose in the victim after disfiguring her
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.