What the fuck. Why are all these huge libraries so...

What the fuck. Why are all these huge libraries so addicted to all the shady crap like dynamic class loading. Just, like, use the classpath, maybe? It exists for a reason.

Like 20 November at 0:11 | Open on mastodon.social

13 comments

Gregory

Context: https://location.foursquare.com/resources/blog/products/foursquare-open-source-places-a-new-foundational-dataset-for-the-geospatial-community/

20 November at 0:12 | Open on mastodon.social

Gregory

Finally. Had to add one more dependency

20 November at 0:35 | Open on mastodon.social

Gregory

First observations:
- Object and category IDs are 12 bytes long (of course I'm not going to store them as these hex strings) which is odd
- The categories are fine-grained enough that "restaurant" is further subdivided into cuisine-specific ones like "Italian restaurant" and "Asian restaurant"
- Regions and cities are stored as names (strings) and don't have IDs

20 November at 0:50 | Open on mastodon.social

Gregory

I'd have to load this stuff into an actual database to meaningfully explore it any further (for one, I'm really curious to see what's in there in my familiar parts of St Petersburg). Will try tomorrow.

20 November at 0:57 | Open on mastodon.social

Gregory

Now I'll just have to wait while it does its thing.

20 November at 15:16 | Open on mastodon.social

Gregory

Oh for fuck's sake. Why are there places that
- don't have coordinates
- don't have an address
- don't have a country
- don't have a date when they were created?!
What's next, places that don't have a name?

20 November at 15:47 | Open on mastodon.social

Gregory

Also what's this thing with throwing exceptions, especially a RuntimeException, when a value is not present? Just return a null ffs. It's not like it's a catastrophic event that warrants an exception that you can't even meaningfully catch.

20 November at 15:49 | Open on mastodon.social

Gregory

I feel like the more data is in the table, the longer it takes to insert new rows into it. And nope that 10.5 GB estimate wasn't right, it's more like 20-something because of the compression. I misled myself by opening one of the files in a hex editor, seeing meaningful strings, and assuming that it must be uncompressed.