Programming

17313 readers

295 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

217

Which protocol or open standard do you like or wish was more popular? (lemmy.ml)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

264 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

[–] [email protected] 1 points 2 months ago

It worked more like true messaging app less than messages store ( unlike matrix ).

Can you please elaborate this point? I don't understand what you mean by "true messaging app" and why that would be a bad thing?

Requirement of permanent tcp ip connection

Are you sure this is the case? Maybe back in the day, but my understanding is this isn't true anymore

useful feature in xmpp ( like message history ) is optional

Why is user choice a bad thing? There's a wealth of clients that implement the features you want

If something doesn't work in xmpp most people would blame xmpp

This may not be an important point, but from my experience, people always blame the client and not the underlying protocol. If I face an issue with my browser, I'd likely blame the browser before I blame http.