3 ms·
This is mostly crap, to be honest. It's all about messaging. I wrote most of the first version of the wave federation spec (I cannot remember how this happene
by DannyBee 13y ago
This is mostly crap, to be honest. It's all about messaging.
I wrote most of the first version of the wave federation spec (I cannot remember how this happened, but im pretty sure it involved being in Sydney temporarily, alcohol, and Soren being Soren. I'm fairly sure I got the short end of the stick on this one).
It was absolute and complete crap.
But it kinda worked.
We were clear it was a first draft, and folks understood it would completely and utterly change.
Within an hour of publishing it, the wonderful XMPP folks emailed me and asked me to fix a few things (like accidentally using some reserved namespaces/etc), and asked how they could help, pointing out the XEP process, and pointing out we were doing some things others were working as well.
With their help, it ended up as a "mostly sane" spec.
Realistically, pressure comes from improper messaging.
If you tell people "here's our current thoughts, in spec form, this is all gonna change", you can do a lot of work in the open without too much customer pressure.
Now, will this slow adoption?
Maybe, it depends on what kind of product it is.
But the argument that you get this pressure out of thin air is wrong. Pressure is mostly caused by self-inflicted wounds where people are not being clear about the state of the world as they see it.
- btilly 13y agoThat is an excellent point, and I'm glad it worked out for you. What I'd be more curious about is how well it would have aged had it not been discontinued. Comments below suggest that if you had longer to do it you would have done it differently. Which suggests to me that developers 5-10 years later would likely have wanted something quite different. The reason that I'm cautious is that I've suffered through code that has to jump through hoops to remain compatible with something someone thought was a good idea 10 years ago. Things that seem like a good idea now don't always a few years later. When you control both ends, you have a potential upgrade path to fix it. When you don't, you're stuck.
- DannyBee 13y agoBut for most of the API's and protocols we are talking about here, 5-10 years later, developers always want something different, regardless of whether you designed it right or wrong. That's just the nature of the speed of our industry. I'm, of course, not suggesting that you should never try to design something that will last 5-10 years, but in most cases, you can only standardize what people want to use now, and hopefully design a way of extending the protocol to be able to standardize what people want to do in the future as well. As you say, otherwise you have to try to remain compatible with something someone thought was a good idea 10 years ago. That usually means it wasn't a good idea 10 years ago, it was something that 10 years ago, they thought would be good in the future, and they predicted wrong. Past that, sometimes you have to just accept that the useful design life span of some protocols is not going to be as long as some customers would like.
- mortehu 13y agoAre you talking about the base64 encoded protocol buffers here? The Google Wave Federation draft spec reminds me much more of XEP-0239[1] than anything else. As a reminder, here's how to send a tiny update to a wave: <message type="normal" from="wave.initech-corp.com" id="1-1" to="wave.acmewave.com"> <request xmlns="urn:xmpp:receipts"/> <event xmlns="http://jabber.org/protocol/pubsub#event"> <items> <item> <wavelet-update xmlns="http://waveprotocol.org/protocol/0.2/waveserver" wavelet-name="acmewave.com/initech-corp.com!a/b"> <applied-delta><![CDATA[CiIKIAoFCNIJEgASF2ZvenppZUBpbml0ZWNoLWNvcnAuY29tEgUI0gkSABgCINKF2MwE] ]></applied-delta> </wavelet-update> </item> </items> </event> </message> 1. http://xmpp.org/extensions/xep-0239.html http://xmpp.org/extensions/xep-0239.html