• locuester@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      1 day ago

      A RESTful service is (usually as of today) a JSON API. They aren’t mutually exclusive things.

      There’s no black and white definition there.

      However, when someone is creating a RESTful service, they’re stating that they’ll be paying mind to HTTP Verbs and status codes as a fundamental part of their design.

      In the original image posted, that dev clearly wasn’t paying mind to the HTTP layer and as such a commenter called it just a “JSON API”, which is the catchall, ugly, Wild West, typical way of doing things (always return 200, errors are in the json).

      Once again tho, it’s not black and white. Others can and will disagree and want to be pedantic. I’ve been a professional dev for 35 years, devs love to argue abt this shit.

      • luciferofastora@feddit.org
        link
        fedilink
        arrow-up
        1
        ·
        12 hours ago

        devs love to argue abt this shit

        Devs and standards have a contentious relationship.

        If I develop something, I obviously know what works best for me, so I don’t want to be constrained by some dumb standard. If someone else doesn’t follow them and it makes things harder for me, they’re a clueless fuckwit that shouldn’t be allowed near a computer ever again.

        Yes, that’s a double standard: I don’t even have a standard when it comes to handling standards.

      • 0x0@lemmy.zip
        link
        fedilink
        arrow-up
        2
        ·
        19 hours ago

        devs love to argue abt this shit.

        Tabs vs spaces comes to mind.