Garbage Ideas

ITT: Post those lame software development ideas you have in the ideas.txt that you are sure you will never get to try them out.

>>43
I don't want to sent a date string or a timestamp. I want to send a date. I want account.expiry_date to be a date so I can compare it to the current date, show it as a string or check the day of the week.
One thing I absolutely do not want to do is litter my code with json_date_to_real_date(account.expiry_date), because after I parse something, I expect it to be fully parsed. The type of the data should be in the data, not in the code that uses it after `parsing'.

Of course XML has its flaws, but when it's a huge pain to just to send a date in JSON¹, you know something's wrong there too.

¹ http://weblogs.asp.net/bleroy/archive/2008/01/18/dates-and-json.aspx

>>46
No, I think JSON sucks because there is no standard way to extend it with user-defined types. With Crockford making ridiculous statements like ``JSON is not extensible. It does not need to be.''¹ it is no suprise that using JSON often results in trying to put a square peg into a round hole.

>>47
Is {'expiry_date': date('2010-09-09')} or equivalent too much to ask for? You could use the identity function by default.

¹ http://www.json.org/fatfree.html