Comment

Comment by danShumway

The Bible isn't that large in terms of actual data, it's all text. So storing a bunch of translations locally seems pretty easy. And from what I can see from the documentation, this only allows querying chapters/verses across translations, so it doesn't seem to be doing a lot of serverside work to link data together or to find references to names/places, or to merge translations together in some way.

Is there a reason I'm missing why this is an API instead of something handled locally in a structured data format? Does it have access to a bunch of licensed translations that I couldn't use locally or something?

I guess I'm just a little confused at what the value add is of having be online instead of local.

parent danShumway 5 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton