It’s true some patents hold, and some lock-in gets built on. Look at PDF for example. But there’s a reason HTML took us places PDF never could. The ability of anyone to do anything they wanted to, without having their API key revoked. That’s a big enabler of creativity, to use terminology VCs understand.
Spending as much time in the future as possible with technology, interfaces, and design.
Collated and written by Matthew Licata. I'm @miraimatt on Twitter.
How do you balance functionality and design?
Jony: A beautiful product that doesn’t work is ugly. The best things we’ve done are harmonious. I think design is the whole thing. Beauty is in that it works.
Ive also spent a section of his panel ‘geeking out’ about design, noting that ‘for hundreds and hundreds of years, the objects we’ve designed or made, the form is the function.’ But with devices powered by silicon chips, the function and form are disconnected — ‘these products could look like a banana.’
Ring ring ring ring ring ring ring, Bananaphone.
Font Rules and Chrome 37 for Windows: Gill Sans, Gills Sans MT vs. Gill Sans MT, Gill Sans
A web development mystery: I received reports that one site I maintain had fonts looking very strange in Chrome for Windows, but not in IE for Windows or in Chrome for Mac, and this was a new problem that only started occurring recently. Nothing had been changed on the site, so my first theory was to chalk it up to a strange font collection situation on one person’s computer. But then I received a second report confirming the same issue on another computer.
The font-family rule that was causing the problem was:
font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
After doing some digging into fonts included (and not included) with Windows and Mac operating systems, and trying and failing to replicate the issue on some plain Windows virtual machines, I found that Microsoft Office was also a part of the situation.
Microsoft Office for Windows includes among its fonts the standard set of variants of Gill Sans MT, but only the Ultra Bold and Ultra Bold Condensed variants of Gill Sans. Previous versions of Chrome (and whatever version(s) of IE those reporting the problem had on their computers) don’t consider the presence of Gill Sans Ultra Bold to be sufficient, and thus move onto Gill Sans MT, but Chrome 37 considers Gill Sans Ultra Bold a workable choice and uses it. Gill Sans Ultra Bold is a fairly ridiculous font for general usage, so this produced the quite undesirable result that had been reported.
(Where does Mac OS X fit in here? OS X includes the standard suite of variants for “regular”, non-MT Gill Sans, which is why the problem wasn’t visible on OS X at all. Office for Mac seems to add the Gill Sans MT family.)
"Gill Sans", "Gill Sans MT", ...
"Gill Sans MT", "Gill Sans", ...
did the trick. After doing so, properly weighted fonts are displayed in Chrome for Windows as well as everywhere else.
It does mean that people on Macs with Microsoft Office installed are now seeing the Gill Sans MT that came with Office instead of the Gill Sans that came with Mac OS X, but I think that’s OK. I haven’t looked closely enough to know anything about the differences between the two, to be honest.