• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: August 5th, 2024

help-circle
  • Many GraphQL and gRPC APIs do exactly that and return HTTP 200 even if the request didn’t auth.

    Just because you are heavily biased toward using HTTP status for application layer errors doesn’t make it right. It is so wildly common that people can’t imagine it working another way, and I get that.

    But it’s not “wrong” to do application layer auth status codes and apply no transport layer auth status codes It’s just a different paradigm than most devs are used to.


  • What do you mean? You can literally run GraphQL without HTTP. This isn’t just a GraphQL-ism, gRPC also does it https://grpc.io/docs/guides/status-codes/

    I understand that most people use GraphQL over HTTP and that from a developer perspective you’d rather have HTTP status codes like every other REST API. To which I’d say, why don’t you just use REST instead?

    There are a bunch of legitimate reasons why a clean separation of transport layer and application layer makes sense - you just aren’t using them so it feels like an arbitrary frustration to you.

    Have you ever run an application like a golang REST API behind an envoy or nginx proxy or load balancer and gotten an HTTP status 500 back and wrongly assumed it was coming from your application/golang code, only to later find it was a problem at the proxy or load balancer? If so, you’ve experienced the misdirection of combining transport and application layer being forced to share a status field. This isn’t a trivial example - time is wasted every day by developers misdiagnosing errors originating from transport as application errors, and vice versa.

    You might not like it, but separating them IS smart design.



  • porkloin@lemmy.worldtoMicroblog Memes@lemmy.worldClever man
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    I think you might just be describing the fact that humans suck and lack empathy rather than a specific mode of transit sucking. Everyone seems to expect that the burden of “paying attention and being empathetic” belongs on others. Sure, there might be some negligible affinity for one mode or another among the biggest assholes, but I’m a firm believer in the fact that 90% of people are just petulant asses who will pay zero attention the moment they get into their car/boat/bike/scooter/moped and then turn around and winge about the injustice of it when someone does it to them the next time they’re on foot. I don’t expect decency from other humans because I’ve seen what they do to public restrooms and places when they think nobody is watching. Immediate reversion to their inner goblin.





  • I’m not OP but I am a long time DA fan (in the sense that I have played each game as a non-completionist at or shortly after release, and have often listed Origins as one of my favorite games of all time) and I’m right there with you on the previous games. I found the game totally fine. It was on par with inquisition and better than DA2 imho. If you liked the others and are a fan I think you’ll enjoy it well enough. Sure, some of the dialogue and story is a little stiff, but I think people have rose colored glasses on when they remember DA:O’s story.

    It’s really hard to get people’s real opinion about the new game because a lot of them just wanna use it as a culture war proxy and either hate it because it because they’re anti-LGBTQ, or vehemently defend it to show how pro-LGBTQ they are. Both groups are annoying even though I am a leftist. I don’t really give a fuck about any of that in the context of the game. The game is fun and anyone who is obsessing over the game for political/social stuff probably didn’t actually play it, because it’s a tiny tiny portion of content in the middle of a huge game. People just want to paint this as a bellwether on the future of wokeness in games, when in reality it’s just a bellwether on if people are still into the same ol (fun as hell) BioWare formula.