“I skate to where the puck is going to be, not where it has been.”
—Wayne Gretzky
The web is changing.
Before, our biggest worries were the diversity of browsers. How do we get CSS to work across both IE6 and Firefox, let alone Safari.
While cross-browser design is still a challenge, those difficulties have eased with time. Modern versions of Internet Explorer are relatively on par with other browsers.
The web controversy du jour: Opera confirms WebKit prefix usage.
Many others have written wisely on why this does or doesn’t break the web. So let me put this more simply.
The new iPad has arrived, most notably with a retina display with four times as many pixels as the previous display. The new iPad has 2048 by 1536 pixels, for an amazing resolution of 264 pixels per inch.
The increase in resolution, and thus the increase in file sizes, has some concerned. Stephanie Rieger wrote last week in “Not In My Best Interest,” that “Sure, the fonts are so crisp they could cut glass, but absolutely everything else on screen is fuzzy.”
There are understandable concerns with delivering graphics with huge file sizes over limited mobile bandwidth. Even over home wi-fi, the graphics are large and will take time to load.
Despite the legitimate practical concerns, I think what some are missing is something easy to lose sight of:
The opportunity to create a magical experience.
I have already said a lot of what I want to say about vendor prefixes, but here’s one more tidbit.
Removing support for prefixed CSS features, when a feature is considered stable, seems counterproductive to me. Here’s why.
The Prefixolypse is upon us.
For the past few years, one of the ways CSS has advanced is through the use of vendor prefixes. According to the minutes from a recent CSS Working Group meeting, that framework may be about to collapse.
Here’s my take on the coming Prefix Armageddon.
Andy Budd wrote a great post on Web Design Disciplines Explained Through the Medium of Dungeons & Dragons. Go read the article: I’ll wait.
If you have never played an RPG, his post or mine are probably not for you. If, however, you fondly remember days of tabletop gaming, read on, as I have a few more thoughts on this great analogy.
A big change is coming with Adobe this year: In 2012, Adobe will be launching the Adobe Creative Cloud. I think this will make a big difference for Adobe users. Here’s why.
Stephanie Rieger, in her posts, “The ‘trouble’ with Ice Cream Sandwich” and “The ‘trouble’ with Android”, points out the myriad little ways that the pixel width of the browser can differ from the default pixel width of the device, from zoom levels to text scaling to browser views embedded within apps that have chrome on the sides of the browser.
Today was my first time attending a City Camp or any conference that used an unconference format.
I’ve helped plan a “normal” conference, so I was curious how an unconference would work in comparison.
I’m sure unconferences vary. Here’s my take on the one I attended.
Otto Doll, CIO of Minneapolis, led a great discussion on open data. Here are my notes on that discussion.
The city of Minneapolis has a lot of data. That gets put together in information presented to the community by the city. However, what raw data should be shared publicly? (Not all data can or should be shared.) How is that data shared? If we put this data out there, do we put it out there forever? Do we keep publishing it forever? Archiving it forever?