Theme 1 – Massive literary works as size/performance benchmarks
“I used War and Peace to explain to a CEO how wasteful a mobile API was; twelve distinct items of data to display but we sent JSON larger than War and Peace.” – timclark
“Good idea, I might use Crime & Punishment!” – N_Lens
“I use War and Peace for this.” – miiiiiike
Theme 2 – Perceived bloat in classics and how readers cope
“This reminds me of ‘The Jules Test’. Popularised (hyper locally) by my friend Jules.” – jonplackett
“Both (IMHO) are much longer than they need to be.” – znpy
“I think at that point in my life I quite enjoyed how much he laboured the details… I just jump around a few pages if I get bored.” – ehnto
Theme 3 – Real‑world software performance with huge texts
“Logseq … put a five‑page file … into ‘read‑only’ mode because apparently at about 1 k characters … the app couldn't handle the performance impact.” – barrin92
“Even that takes seconds to start on my M1 Max from cold. So then I just wrote … a viewer app … computers are so fast you can open multi‑GB JSON files instantly.” – arjie
“You had me at ‘dick workout’.” – hnbad (shows the humor around the topic)
These three themes capture the core of the discussion: using epic books as size tests, debating their length and how to navigate it, and highlighting performance challenges when handling such large texts in software.