"The things which I’ve painted as trivial here are admittedly anything but. But they are, I sincerely believe, how we’re going to handle — have to handle — the human interface to this so-called Internet of Things we keep talking about. Each of the networked resources in the world, whether location or service or object or human being, is going to have to be characterized in a consistent, natural, interoperable way, and we’re going to have to offer folks equally high-level environments for process composition using these resources. We’re going to have to devise architectures and frameworks that let ordinary people everywhere interact with all the networked power that is everywhere around them, and do so in a way that doesn’t add to their existing burden of hassle and care.

"the corpus of people able to develop functionality, to “program” for a given system, has been dwindling as a percentage of interactive technology’s total userbase…Alan Kay’s definition of full technical literacy, remember, was the ability to both read & write in a given medium — to create, as well as consume. And by these lights, we’ve been moving further & further away from literacy & the empowerment it so reliably entrains for a very long time now. … we need to articulate a way of thinking about interactive functionality & its development that is appropriate to an era in which virtually everyone on the planet spends some portion of their day using networked devices; to a context in which such devices & interfaces are utterly pervasive in the world, & the average person is confronted with a multiplicity of same in the course of a day; and to the cloud architecture that undergirds that context. Given these constraints, neither applications nor “apps” are quite going to cut it"

"early precursors to the web, different versions of hypertext, early thinking that went on around how networked information systems. It’s interesting - not just historically, but also relevant to today ont he web - if you look at the history of technolo