Hacker News new | ask | show | jobs
by milestinsley 5981 days ago
This is pretty cool and worth noting for future project, but I can't help thinking it makes more sense to do this server side.

It would be more useful, to me at least, if it converted user inputted "cute dates" (i.e 3 days ago) into a compliant timestamp (i.e 2010-1-29 20:13:00).

2 comments

Client side is good when you are viewing new items and leave your window open for awhile. The script can run again and update "a few seconds ago" to "a half hour ago".
Of course. That's a good use case.

Thanks :)

Additionally, this type of technique works great with content caching.
If you're handing dates straight back into the interface sure, but if you're calling an ajax api or similar it may be better on the client side. Twitter for example, nice dates on the web and in clients, the ajax stuff gives the long ones.