221
Which protocol or open standard do you like or wish was more popular? (lemmy.ml)
submitted 2 years ago* (last edited 2 years ago) by to c/programming@programming.dev
267 comments fedilink hide all child comments
 

There are a couple I have in mind. Like many techies, I am a huge fan of RSS for content distribution and XMPP for federated communication.

The really niche one I like is S-expressions as a data format and configuration in place of json, yaml, toml, etc.

I am a big fan of Plaintext formats, although I wish markdown had a few more features like tables.

you are viewing a single comment's thread
view the rest of the comments
[–] 15 points 2 years ago (8 children)

Problem Details for HTTP APIs - I have to work and integrate with a lot of different APIs and different kinda implementations of error handling. Everyone seems to be inventing their own flavor of returning errors.

My life would be so much easier if everyone just used some 'global unified' way to returning errors, all in the same way

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 9 points 2 years ago (4 children)

    Please guys, stop using line-breaks mid-sentence. It's not the 90's anymore, viewers generally can wrap.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 years ago (3 children)

    Maybe a bad markdown viewer?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 years ago* (2 children)

    viewer generator?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    No, in general the markdown format suggests using line breaks in the middle of paragraphs to make the code just as readable as the output. That’s why two line breaks is what creates a new paragraph. So it’s the viewer showing it incorrectly here.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 years ago* (last edited 2 years ago)

    Saving...

    I made my first API at work last year (still making) and always saw myself looking for input on making a consistent way to return errors, with no useful input from the senior programmers or the API users. This is my second biggest problem, the first being variable and function names of course.

    If I were to do anything related to HTTP, I now have something to look at.

  • permalink
  • fedilink
  • source
  • parent