[acqq]

Independently of the fact that I'm thoroughly against the use of proprietary algorithm for encoding, there's an interesting problem of the implementation of a range of similar problems to which somebody here maybe knows a nice effective solution:

(from their FAQ):

"The JavaScript library is about 2.4 megabytes. Almost all of this data is encoding data about how regions of the Earth are mapped to n values. There are over 300,000 regions. The raw data for the regions is 1.8 megabytes, and getting the data encoded in a JavaScript file raises this to 2.4 megabytes even after compression.

The Go library is about 2.6 megabytes of source code, for similar reasons, and produces executables of at least about 5.7 megabytes.

If you can shrink any of this data or make any other improvements, then please contact us and we will be pleased to use your improvements."

[londons_explore]

For the go executable to be so much larger than the source code, when he majority of that is data, there must be something going wrong...