Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My only gripe is that the tile metadata is stored as JSON, which I get is for compatibility reasons with existing software, but for e.g. a simple C program to implement the full spec you need to ship a JSON parser on top of the PMTiles parser itself.


A JSON parser is less than a thousand lines of code.


And where most of CPU time will be wasted in, if you care about profiling/improving responsiveness.


At that point you're just io bound, no? I can easily parse json at 100+GB/s on commodity hardware, but I'm gonna have a much harder time actually delivering that much data to parse.


What's a better way?


How would you store it?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: