This resonates but I think there's a framing issue. From building educational coding tools for kids, what I've observed is that the volume of textual engagement hasn't necessarily dropped — it's migrated to different forms.

An 11-year-old debugging a Python script is doing intense, sustained reading. Parsing error messages, reading documentation, tracing logic through nested conditionals. A kid building in Roblox Studio is reading and writing Lua. These are literacy acts — just not the kind that show up on NAEP scores or novel-reading surveys.

The real gap isn't hours logged. It's transfer. The kid who can read 200 lines of GDScript to debug why their character won't jump doesn't automatically transfer that stamina to reading a history textbook. The cognitive muscles are being built, but they're specialized.

From what I've seen, when you meet kids where they are — letting them read and write code to solve problems they care about — they'll happily put in hours of focused textual work. The appetite is there. We're measuring the wrong meal.