Something you miss is that the central directive for the iPad was a consumer experience. It's intended to be roughly equivalent to a TV. It's great that you choose to use it for Discovery Channel and the like, but you're probably not using it to write code. And that's fine; it's not meant for that. And that's the point: it's not meant for that.
Incidentally the original Macintosh did not grant shell access to the user either, and for that reason was a favored web server platform of certain DOD programs. Those worried that Apple is closing off the possibility of programming should consider a longer view: with OS X, Apple introduced shell access to their OS, which is a certified Unix. Even with Mountain Lion, they are still introducing additional CLI functionality.
http://www.tuaw.com/2012/07/30/new-command-line-tools-in-mou...
A better word might be 'passive learning'.
Consumption without purpose is pointless. Your case may be an exception, but unfortunately I think it's more of a rarity than it is a representation of the common use of the device.
I'm getting sick of this "iPad is for consumption" thing. How are you going to "produce" something if you haven't learned anything yet? For me, iPad is a learning device. In the past year, I've read maybe 15 (technical) books on my iPad. I wanted to read them for the past 3 years, I had downloaded their ebooks and stashed them neatly in a 'To-Read' folder, but never get to do so on a Mac or PC because of their form factor.
In the past 2 weeks alone, I read 'JavaScript: The Good Parts' and first 5 chapters of 'Git Pro' (ePub, in iBooks), 70% of 'Head-First C' (PDF, in the fantastic ReaddleDocs[1] app) and 20 other technical/"intellectual" articles in Instapaper. Without iPad, I wouldn't have read them.
---
[1]: http://itunes.apple.com/us/app/readdledocs-for-ipad-pdf-view... - Believe me, this app is fantastic. You don't know how great it is until you use it.