4 ms·
If you're going to compare yourself to an existing library, you really need to explain the trade-offs you made in comparison. Even if all of the corners you cu
by always_good 9y ago
If you're going to compare yourself to an existing library, you really need to explain the trade-offs you made in comparison.
Even if all of the corners you cut were 58kb of code bloat, that would be exactly the information we'd want to know.
So, what exactly was left on the cutting room floor? For example, I can see there are no localization files. What else?
- tbrock 9y agoTime-zone support is one. The thing i don’t get is why for libraries like moment don’t we host the tz data on a cdn and have the library just request the cached copy at runtime? Or better yet, have the browser supply it as part of the browser api. We are boiling the oceans compiling this into our JS.
- RandomBK 8y agoRegarding your CDN suggestion, that is already effectively the case if the library is hosted on a CDN. Creating a hybrid baked-in/CDN solution is only going to complicate the situation with little to no improvement. However, it would be great if more datetime functionality can be baked into the standard library.
- scottmf 8y agoThere’s a stage 1 proposal for better date/time features https://github.com/tc39/proposal-temporal https://github.com/tc39/proposal-temporal
- sametmax 8y agoTime zone is the main reason to use moment.js. it's like saying you jave a jquery competitor, but you removed ajax and events support. But hey you can still do dom manipulation.