[tz] Request to add entry to "Programmatic interfaces that map geographical coordinates"
gilmoreorless at gmail.com
Mon Dec 12 21:54:44 UTC 2016
I keep a bit of an eye on the Node.js ecosystem for tz-related projects, and I also recommend not linking to the “timezone” keyword page on npmjs.com
Many projects listed on that page are API wrappers of the moment-timezone project, and some are integration points for frontend frameworks. Many others are small scripts written by people who clearly haven’t encountered the ambiguities and ever-changing definitions that happen when dealing with time zones. For example, I know of one package that simply returns the UTC offset of a named time zone, but completely fails to account for daylight saving time.
A low barrier to entry means digging a bit to find the good stuff. When it comes to the Node ecosystem, a curated list of known high-quality projects is always better than linking to a keyword search.
> On 13 Dec 2016, at 4:20 AM, Evan Siroky via tz <tz at iana.org> wrote:
> The package tz-lookup and geo-tz are independent of each other. As far as I know, the major difference between the two is the data source that is used. geo-tz is released under the MIT license.
> Feel free to link to the timezone tag. Although in my opinion a lot of the packages aren't the best because they don't get updated frequently enough with changes to the timezone db.
> On Saturday, 10 December 2016, 12:02, Paul Eggert <eggert at cs.ucla.edu> wrote:
> In looking at <https://www.npmjs.com/browse/keyword/timezone <https://www.npmjs.com/browse/keyword/timezone>> I see several more
> Node.js time zone packages that seem relevant. Perhaps we should link to that page?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tz