July 12, 2010
HTML isn’t about Web pages
That assumption is that Nack is talking about creating web pages. I don’t believe he is… This is not the web Zeldman is interested in. It’s no web at all, in fact. [...]
Look at any of Apple’s stores on the iPad – App Store, iTunes Store, iBookstore. Heck, look at the iTunes Store on your computer: it’s all made with HTML and CSS. Why? Because in the year 2010, if you’re going to be describing layouts, it’s not a bad call to describe them using very well adopted, rapidly developing technologies. [...]
There’s no pride or glory in tweaking number after number and reloading a page to make sure my drop shadow looks nice.
On this last point, I’m hopeful that if Photoshop made it possible to copy/export styled text and objects as HTML/CSS, developers would accept the generated code. There are only so many ways to specify box dimensions & borders, right?
More broadly, people are clearly interested in doing demanding, print-quality typesetting using HTML, the better to create things like magazines for tablets. I’m encouraged to see work that enables better text breaking, kerning pairs & ligatures, proportional leading, and more. Onward and upward.
One other thing: I’ve gotten to know Neven a bit after he (justifiably) needled Photoshop for its admitted hodgepodge of UI elements. I’ve never managed to finish my long and detailed response, but in it I talk about how using Web elements (e.g. embedded WebKit) makes it hard–if not impossible–to match everything with OS-native controls. I go on to cite numerous examples of Apple’s Web content not matching Aqua, etc. The point is, the more powerful & ubiquitous Web content becomes, the more we’ll deal with the challenges of making the complete desktop/online experience feel cohesive.