I interpreted it as "Software is crap, and it's hard to make crap work offline. The problem is not the offline, it's the crap."

The question is where to lay the blame for the crap, and how to change that.

I would love to see the author's "lists" turned into a table of sorts, and then any given piece of software could be rated by how many situations on each list it works in without modification, works in with trivial config tweaks, works in with more elaborate measures, or cannot work in. Turn the whole table green and your software is more attractive to certain environments.