@AbyssalMonkey
Would probably kill any mobile device. That also seems like a metric shit ton of data.
Maybe, maybe not. they could separate it per language and just put the most basic info on some format like |40248;34..|44110:1 ( |ID;Count )(used real IDs btw)
doesn't have to be human readable
a simple script could do all that, they can just pre sort it before publishing it and just retrieve the content in order with a single query
they could easily implement this since it's mostly independent to their database
assuming that mangadex titles its mangas incrementally, as of writing this, mangadex only has 44,112 mangas
with the formatting system i casually proposed earlier (|ID;Count)
assuming that every manga has 3 digit chapter counts i.e. 999 in total for all languages, storing all the data would only amount to 441.12 kB (10bytes * 44112)
that's less than half an MB, with 42 languages that equates an average of 10.5 kilobytes per file which isn't really alot
the JS just has to query 40 mangas in sequence and they'll be finished i.e querying the first 40 mangas, and querying the next when needed
doing it this way is a possible bypass to any bottlenecks they might have since everything have already been pre sorted and the server would only recieve a single simple and neat query.. i.e
SELECT * FROM mangas WHERE id IN( ID1,ID2...,ID40 )
heck, they could even host the file in github like how adblocker list are hosted there