On Tue, May 12, 2009 at 10:23 PM, Tim Bray <Tim.Bray@sun.com> wrote:
For JSON it's a lot less clear (at least for the famous enterprise users)
due to the support, copyright, patent, etc. status surrounding third-party implementations. I know at least some of my clients have policies that would require developers to write the parser themselves - granted not a particularly difficult task but an unnecessary and error prone one.
We must live in different worlds. The Java programmers I know are like "Yeah, JSON, whatever", and for .NET, http://www.google.com/search?q=json%20.net turns up lots of stuff including from Microsoft's own Codeplex. Javascript/Python/Ruby, no problem. PHP I have no first-hand info, but since half the Ajax-heavy sites in the planet are PHP-backed, I can't imagine it's an issue. -T
Perhaps we do [live in different worlds]. Where I come from people would rather have silent phones<http://blogs.gartner.com/lydia_leong/2009/05/11/the-perils-of-defaults/>than risk changing a default setting. Opaque binaries and their updates pass without question while third-party/open source implementations are held up for months in convoluted approval processes (if not flat out banned). "Simplicity" translates to "Complexity" (so does "Complexity" for that matter). One of the reasons I'm pushing the point is because I'd actually like to be permitted to use the fruits of our labour. Sam