It seems this transformation, from physical object to vector of data, is a general and oft-repeated process in the history of technology, where new inventions begin in an early experimental phase in which they are treated and behave as singular individual things, but then evolve into vectors in a diffuse and regimented system as the technology advances and becomes standardized.
In the early history of aviation, airplanes were just airplanes, and each time a plane landed or crashed was a singular event. Today, I am told by airline-industry insiders, if you are a billionaire interested in starting your own airline, it is far easier to procure leases for actual physical airplanes, than it is to obtain approval for a new flight route. Making the individual thing fly is not a problem; inserting it into the system of flight, getting its data relayed to the ATC towers and to flightaware.com, is.
Which would you choose: a world with pyramids? Or without?
Humanity has always dreamt of flight, but the dream is cursed. My aircraft are destined to become tools for slaughter and destruction. But still, I choose a world with pyramids in it. Which world will you choose?
A piece of milled plexiglass acting as a projecting lens; via the Computer Graphics and Geometry Lab at the École Polytechnique Fédérale de Lausanne
New milling techniques applied to glass and plexiglass panels could be used to “create windows that are also cryptic projectors, summoning ghostly images from sunlight.”
[Pauly and Bompas] hope that the technique will be used in architectural design, to create windows that mould sunlight and throw images or patterns onto walls or floors,” which, if timed, milled, and manipulated just right, could produce a slowly animated sequence of images being projected by an otherwise empty window during different times of day.
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?