You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using tz-lookup-net but the package and the underlying timezone data hasn't been updated for more than four years, therefore I looked for an alternative and found this project. Unfortunately, it appears like this package is much, much larger in size (over 3 MB vs ~100 KB), likely because the timezone boundaries are more precise.
3 MB is just too large for me to be using it in a mobile app (it would make up 10% of the total app size).
According to tz-lookup-oss (the repo on which tz-lookup-net is based on), they were also using timezone-boundary-builder as source for the timezone data - just like this package - but perhaps with some additional lossy compression, resulting in the much smaller package size.
It would be fantastic if this library could offer something similar. A "GeoTimeZone-Lite" variant that is 40x smaller than the current version would be worth the tradeoff for slightly less accuracy for me
The text was updated successfully, but these errors were encountered:
I am currently using tz-lookup-net but the package and the underlying timezone data hasn't been updated for more than four years, therefore I looked for an alternative and found this project. Unfortunately, it appears like this package is much, much larger in size (over 3 MB vs ~100 KB), likely because the timezone boundaries are more precise.
3 MB is just too large for me to be using it in a mobile app (it would make up 10% of the total app size).
According to tz-lookup-oss (the repo on which tz-lookup-net is based on), they were also using timezone-boundary-builder as source for the timezone data - just like this package - but perhaps with some additional lossy compression, resulting in the much smaller package size.
It would be fantastic if this library could offer something similar. A "GeoTimeZone-Lite" variant that is 40x smaller than the current version would be worth the tradeoff for slightly less accuracy for me
The text was updated successfully, but these errors were encountered: