This report about Google’s brand power reminds me of a discussion I had with a guy from Adobe at ETech who was pushing Apollo. I was trying to figure out why somebody would want to use it, and this guy’s response was “One word; branding”. Of course, he trotted out the expected example of Apple and iTunes and said that iTunes was more immersive and therefore provided Apple superior branding. Ok, fair enough. But obviously, as this report shows, Google didn’t require a fat client in order to build one of the world’s strongest brands.
Adobe’s ability to execute has been impressive, of course. But I can’t help but wonder if they wouldn’t be doing so much better had they simply innovated on top of the Web. I suppose that’s the easy way out, but it’s not nearly the most lucrative.
Dave Orchard on versioning;
The fundamental problem with a version # in a document is that it doesn’t provide for a given document to be valid under more than one version. What we really need is to be able to indicate a “space of versions” that a given document is valid under, whether that’s a list or regexp or whatever.
Amen. You know, just like a media type!
A quaint exchange
on the WebAPI WG mailing list;
>> Why not always uppercase method?
>
> That would upset the HTTP gods.
Ok. Fair enough.
I see that my work there is complete. 8-)
I’m very happy your baby is 42 weeks old, and that you’ve chosen pampers for it, and that you like recipe collecting. But please note that mbaker@gmail.com is not your email address. Thank you.
I’ll be well out of range of an IP packet next week when it happens, but next Tuesday marks the seventh anniversary of my first public anti-WS post, to Develop Mentor’s old “soap-discuss” mailing list.
I didn’t realize it until now, but James Snell gets the dubious honour of being the target of that post. It’s like he’s Steve Trachsel to my Mark Mcgwire 8-).
That is all.
Don’s latest on GET is interesting (especially “That’s certainly where I’m investing”!), but I really liked this bit of
Tim Ewald‘s comment;
The solution is a minimal footprint interaction, like a coarse-grained document transfer via a pin-hole, a la’ a Biztalk port. Exposing all your data via GET so anyone can read anything they want (modulo security concerns) and then providing controlled writes through pin-hole ports that consume documents and encapsulate the actual update process.
Bingo! Give the man a cigar.
That said, once you’ve done that for a while you will, in all likelihood (I’ve been there), find the need for the client to have expectations about server-side state changes beyond those offered by POST; PUT and DELETE are two very useful expectations.
The view of my GMail spam folder;
Is this just Google being cute or an unfortunate search result? Either way, pretty funny.
Well, maybe not “galore”, but it looks like Leonard and Sam
may have some
competition
on their hands; this one’s Java-specific though.
I wonder what ever happened to Kendall’s?
I’ve decided to drop the daily del.icio.us links that get posted here. If you still want to subscribe to them, feel free.
The main reason for this is because I have – quite unintentionally – been using the links as a substitute for actually writing something of substance. That’s bad.