To... read between the lines... on this summary, I think The Zen of Python is applicable here. Readability counts.
One technique that might work would be to "translate" content into a simpler language which is optimized for fast serial consumption with high comprehension. Sure, that's probably impossible to achieve with today's technology, and there's the issue of internationalization (is it a version of an exisiting language with strict rules, or a whole new language altogether?), but those are "just" engineering problems, right?
Or maybe the inverse is really the problem - maybe it's not the language, but the metric we're focusing on. WPM is as poor of a metric for "rate of information intake" as LOC is for programmer productivity.
One technique that might work would be to "translate" content into a simpler language which is optimized for fast serial consumption with high comprehension. Sure, that's probably impossible to achieve with today's technology, and there's the issue of internationalization (is it a version of an exisiting language with strict rules, or a whole new language altogether?), but those are "just" engineering problems, right?
Or maybe the inverse is really the problem - maybe it's not the language, but the metric we're focusing on. WPM is as poor of a metric for "rate of information intake" as LOC is for programmer productivity.