Because it is like we're not writing a renderer — we're not writing a systems level like WebGL renderer. Instead, the browser is our render, and so we need to have as much knowledge about how that thing works as we would if we were working with a lower level architecture.
We don’t want to make websites instead of books. To understand what a digital book should be, it’s worth trying to perceive it as an information format, not a physical medium.
With this experiment, we wanted to explore the uniquely dynamic capability of software, which are hard to replicate in a printed, linear medium, for writing.
Each jewel of Indra’s Net includes the reflections of all the other jewels; the significance of this symbolism is that each entity in the universe contains within itself the entire universe. This idea, rather than positing interdependence among separately existing entities, asserts that the whole does not owe its existence to the coming together of... See more
I think we’ll see communities of users craft downloadable ITEs specific to certain kinds of work or workflows. [...] These kits are a kind of “hypertemplate.” They provide a kind of pre-fabricated foundation for knowledge work that users can share to help others get started. At the same time, power users will use these to capture many aspects of... See more
Most designers set requirements for f() by describing what f() should be, which is a circularity. To be useful, requirements should be defined independent of f() as tests for fitness.