I posted back in August my thoughts on XML vs JSON, and since then I have to admit to warming up to JSON a lot more. The reason is simple, and by that I mean JSON is simple -- and it's not just JSON itself but the JSON ecosystem, which is also simple. As with anything good, people can't leave well enough alone and so we now have standardization efforts of JSON namespaces, schema, patterns, etc...
So when I saw that there was a binary encoding for JSON, BSON, I didn't know whether to laugh or cry. What is it about computer science that the same thing has to be reinvented five times? We must have a lot of idle hands, which I find odd considering programmers are still commanding good salaries in these hard economic times.
So for the love of all that is good, I ask that everyone stop it. JSON doesn't need anything it doesn't already have. There is no need for JSON namespaces or schemas or binary encodings. If you need those things, use XML or ASN.1 or something else that has already been tarted up.
Friday, December 30, 2011
Wednesday, December 28, 2011
Software Development Developments of 2011
Interesting read for software developers:
Monday, December 26, 2011
The Year In Up and Coming Programming Languages
Rob Diana has an article about going over his predicted aspirations for 9 programming languages for 2011, and what happened to them. Some people put a lot of effort into the "next new" programming language. Keep in mind, such a thing was highly popular in the 1970's too. Though the history of modern computer science isn't long enough, perhaps this exploring-new-avenues thing is a cyclical trend.
Subscribe to:
Posts (Atom)