Smart Time Ago: a new JS lib to update relative timestamps more efficiently
1–10 of 14 posts
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#2This is such a minor tweak that I can't see how it's worth trouble of downloading even a byte of extra code to get it done.
Please correct me if I'm wrong.
Edit: "minor tweak" in terms of efficiency. The processing power saved by making it "smart" is probably less than what it takes to download the extra code.
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#3The regular timeago is on Github: https://github.com/rmm5t/jquery-timeago.
I don't see the need for a new project for something like a tweak like this. Seems like a reasonable pull request for the timeago folks???
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#4This is such a minor tweak that I can't see how it's worth trouble of downloading even a byte of extra code to get it done. Please correct me if I'm wrong. Edit: "minor tweak" in terms of efficiency. The processing power saved by making it "smart" is probably less than what it takes to download the extra code.
[deleted]
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#5The regular timeago is on Github: https://github.com/rmm5t/jquery-timeago . I don't see the need for a new project for something like a tweak like this. Seems like a reasonable pull request for the timeago folks???
Yup. Ryan did a great job on the timeago lib. We have ever discussed about the pull request but finally find that we changed lots of the logic about how to deal with the relative timestamp. So we started a new one to give an optional choice.
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#6This is such a minor tweak that I can't see how it's worth trouble of downloading even a byte of extra code to get it done. Please correct me if I'm wrong. Edit: "minor tweak" in terms of efficiency. The processing power saved by making it "smart" is probably less than what it takes to download the extra code.
It depends on the application itself. For pages which user will only stay for few minutes, no much more efficiency gained. But for realtime apps which user will keep the page open for hours/days, it will improve a lot. And for apps which have more read than write, it will also improve a lot.
BTW, I'm not sure whether I catch you about the "extra code". It's a replacement with less than 1KB difference in size.
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#7you guys might be interested at this; https://github.com/azer/relative-date
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#8you guys might be interested at this; https://github.com/azer/relative-date
It looks interesting. Thanks for the info. Just watched. :D
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#9Javascript relative time displays have hilarious results if the web browser's clock is set incorrectly. That's mostly not a modern problem thanks to NTP being baked into modern consumer OSes but it can be terribly confusing if you have a misconfigured client.
Re: Smart Time Ago: a new JS lib to update relative timestamps more efficiently
#10Javascript relative time displays have hilarious results if the web browser's clock is set incorrectly. That's mostly not a modern problem thanks to NTP being baked into modern consumer OSes but it can be terribly confusing if you have a misconfigured client.
The simple solution to this is that the server sends a reference time along with the timestamps: when the page loads you calculate the drift from the local time to the reference time, and then adjust local time to server time when you update relative timestamps.