Programming

423 readers

3 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 !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

136

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 cyclohexane@lemmy.ml to c/programming@programming.dev

132 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

[–] 0x0@programming.dev 5 points 2 months ago (2 children)

XMPP is very old

Seriously? That's your argument? So is the wheel.

Requirement of permanent tcp ip connection doesn’t work well for mobile

I was under the impression PubSub was created for that.

Still, it's an open extensible protocol.

[–] MonkderVierte@lemmy.ml 2 points 2 months ago (1 children)

XMPP is very old

Seriously? That's your argument? So is the wheel.

They elaborated how that relates; usage scenario changed with mobile phones. XMPP is a bad match.

[–] 0x0@programming.dev 2 points 2 months ago (1 children)

XMPP is a bad match.

The X is for extensible, so are a whole bunch of other protocols and people haven't stopped using them, they get improved upon (for the most part).

[–] MonkderVierte@lemmy.ml 1 points 2 months ago (1 children)

The mentioned permanent tcp ip connection (which you don't neccessarily have on mobile) too?

[–] 0x0@programming.dev 2 points 2 months ago (1 children)

I was under the impression XEP-0060 solves that.

[–] MonkderVierte@lemmy.ml 2 points 2 months ago

Sorry, i won't read that whole thing. But i guess you're right, in which case i take back what i said.

[–] endofline@lemmy.ca 1 points 2 months ago* (last edited 2 months ago) (1 children)

Seriously, if you do take one verse from the whole response, you get straw men you fighting with.

I just told you that jabber / xmpp was created in the times almost nobody knew or believed mobile phones can be a thing. Thus it got created in that way: many similarities of xmpp and e-mail, irc or icq which didn't stand the passage of time.

Of course, you're right xmpp evolved to get PubSub extension as an "optional feature" but because of its availability (or rather lack) - most servers didn't support it even the client did support, xmpp didn't win the acceptance of the end-users. It got some attention in the business world (cisco jabber) but not in the retail.

Business cannot work forever without clients willing to pay or at least use, so it died off even in the business.

End of story, try not to fighting with the straw men you created.

[–] 0x0@programming.dev 2 points 2 months ago

Of course, you’re right xmpp evolved to get PubSub extension as an “optional feature” but because of its availability (or rather lack) - most servers didn’t support it even the client did support, xmpp didn’t win the acceptance of the end-users. It got some attention in the business world (cisco jabber) but not in the retail.

That XMPP's extensibility is in itself a strength and a weakness is indeed a valid argument, as you've exemplified. I was expecting you'd criticize OMEMO though...

Business cannot work forever without clients willing to pay or at least use, so it died off even in the business.

No, it didn't die off, it's still used. IRC is still used as well, probably more or less at the same level. But if you define usage as "used in business" well then probably just a few cases, yes.

I hadn't heard of Cisco Jabber but i've heard of Google and Facebook - both companies' messengers were, initially, based on XMPP but they EEE'd it once they got enough users and walled their gardens, dealing a major blow to the protocol.

End of story, try not to fighting with the straw men you created.

Can i fight my inner daemons at least? Please?