First the iPad, and now a debate on the relevance of Flash. Apple continues to ignore it and touts HTML5 as the future. Google is also pushing HTML5 on YouTube, with other video sites starting to follow suit. Even Mozilla is disabling it in its new mobile browser, Maemo. Clearly, the death knell for Adobe’s most controversial product is getting louder than ever.
But it’s still all talk, all noise. How about some real action? Thankfully, over at Binary Bonsai, Michael Heilemann has taken it upon himself to drop Flash for the whole month of February as a response to this tweeted challenge:
All those who think no flash on ipad is A-OK please uninstall flash from your current browser, use that for a month then get back to me.
Installing a Flash blocker isn’t really a groundbreaking exercise and is tamer than uninstalling Flash completely, but now is the best time to figure out how dependent we are on it.
So can you survive sans Flash? I won’t go out of my way to defend it nor suffer from withdrawal without it, but the status of HTML5 video alone seems troubling enough.
More importantly, most discussions cover only the question of replacing Flash video, not other applications like games. That would be an even tougher nut to crack, even with the dawn of purely Javascript-based games.

The Apple iPad has polarized the tech industry in the past week. I’m amused by this development, not in the context of product innovation or what it could mean for web design and development, but for the culture of tech opinions.
There’s the half that believes the iPad is not the revolutionary new step in computing people having been waiting for, and then there’s the other half that thinks those critics are not the iPad’s target market. Considering how Steve Jobs began with his keynote about the iPhone is now dominating the mobile phone industry over veterans Nokia and Samsung, it certainly takes a lot to accept that the iPad might not enjoy the same fate. This short and sweet (which is rare) post by Jeff Lamarche puts things in perspective:
I’m sure somebody has told you all this before, but let me point it out again: it’s not always about you. Products can be successful even if they aren’t right for you.
[...] I’m a techie, but I don’t need to be able to program on every electronic device I own. I don’t hate my dishwasher because I can’t get to the command line. I don’t hate my DVD player because it runs a proprietary operating system. Sheesh.
But my beef with this is: hardly ever does that argument surface when not so popular, not so geek-worthy products surface. From what I’ve seen in tech culture, it’s so much easier to reject, even hate a product than even entertain the notion that it could succeed. In general, in a certain demographic, in a certain geographic region.
At times the word easier gets replaced by cooler. It’s cooler to hate stuff; that’s what techies are supposed do.
See how all the Apple or tech pundits are squeezing out the possibilities where the iPad could work wonders. Will it kill e-book readers? Will it revitalize the newspaper industry? Will it shake up processes in education, art, medicine, and business? Which function was it born to do?—as though it hasn’t been discovered only because Steve Jobs didn’t whisper the answer in their ears.
Is it because of passion for the brand? I would think other products may not deserve the same passion, but they do deserve a fair chance. Don’t hate a product just because it isn’t right for you.
Perhaps now there’s half of a crowd deciding people shouldn’t be so quick to judge, the tradition could change. Or it could not, because Apple is the exception to the rule.
Or as a like to call it: podcasts that have caught my eye in the past week or so. And they differ in several ways, so there’s sure to be something for everybody. Take your pick:

Confession: It took me a while to realize that this podcast is actually the previously-named You Suck at Web Design, relaunched as a new brand with a new site design. This show isn’t so much a bag of tricks on web design as it is a quirky, personal storybook told by Matthew D. Jordan, but still a must-listen.

This is not just one but seven shows tackling different topics, from photography to Ruby programming, founded just last year by Dan Benjamin. I love the idea of a whole network of shows about the internet, on the internet, and here we have a whole suite for people who make websites. I can think of few things better than that. More networks and more topics, perhaps?

In light of the “circuses” happening in both the Hollywood late night talk show circuit and the web working groups, standardista slash comic strip creator Kyle Weems aka CSSquirrel announced this:
I am in the process of devising a “late night” talk show that the Squirrel will host, featuring interviews with cartoon representations of various web designers/developers/standardistas. It’ll draw from the mighty traditions of the Tonight Show, The Daily Show and Space Ghost: Coast to Coast, and in theory will be a plug-in free experience brought to you in part by HTML5, JavaScript and vector tree-climbing rodents.
Check out the podcast over at SitePoint, titled HTML5 is a beautiful mess:
The podcast touches on that matter, and spins out to the state of the actual implementation of HTML5 itself, whether there’s a challenge in getting designers and developers to start using it, the issues of accessibility in <canvas>, and how delightful it’d be to move past plugins.
Truthfully, I’m trying to avoid getting caught in the sticky details of how HTML5 is developing at the moment because it only adds to the anxiety (isn’t stressing over Internet Explorer enough?) and diminishes hope (we’re supposed to be moving forward with these technologies already). But it also helps to stay realistic not just idealistic, and drawing back the curtain on how the working groups are actually working on the HTML5 standard is a good way to do that.
A year or so after Google Chrome was first released, it’s now my default browser. While I still use other browsers on a regular basis, Chrome’s speed and minimalism has taken over. Take the omnibox, which merges the address bar and search bar into one. It searches your bookmarks, your recently visited pages, and even detects if the URL you’re typing has its own site search.

Most of these features are available in Firefox, whether by default or as an add-on, but the reason I’m focused on Chrome is that it’s a Google product, and this company can push both its browser and search forward by turbocharging the omnibox the way they’re continually adding new features to Google search.
The Chrome extension Google Quick Scroll, which highlights and jumps to portions of a page where one’s Google search query can be found, is a perfect example of Google search and the Chrome browser working side by side to improve the search—and more importantly, find—experience.
Google’s autocomplete search box is getting more powerful each day, so why not integrate it into Chrome? It probably won’t matter to those who can’t tell the difference between a web browser and a search engine, and use Google as a jump-off point to browsing other sites, but Google can significantly alter the whole searching-browsing experience if it so desires.
One downside would be eliminating the need to visit Google.com itself and contribute to the ad impressions, but that should only happen for quicker, smarter searches such as weather forecasts, currency exchange rates, stock quotes, etc. The fewer clicks, the better.

So I was reading Elliot Jay Stocks’s post on the Apple tablet and noticed all the fancy gravatars his commenters had (maybe because they were not as small as the ones in the blogs I frequent). One in particularl that caught my eye was Jeremy Swinnen’s and made me wonder if, like Sam Wilson’s, it was a condensed version of his website and/or brand. I visited his site and turns out I was wrong.
Avatars are usually faces (photographs, caricatures, etc.) or logos, because that’s the most straightforward way to advertise yourself. But why not try something that remind people of your own website? Chances are that’s the first thing they do after reading your comment: check out who you are via your homepage.
If the logo in your avatar is featured prominently, which is probably the case anyway, then great. But I feel a disconnect when visiting a site that has no visual ties to the avatar associated with it. And putting a spin in your branding by using more than your logo in an avatar is a worthy challenge.
Sure, we also associate people with their respective URLs, but aren’t avatars the proverbial peacock’s feathers, the smoke and mirrors, the flashing neon sign—to lure people in, establish a connection, and possibly seal the deal on whatever it is you’re “selling”?
If you’re not choosing the most effective way to bring people over from Mr. Stocks’s site, then you could be missing out.
Web standardistas lament the outdated HTML and CSS support by IE6, but the biggest reason you should drop the browser stat is security, security, security. And if the following evidence from Google, the governments of Germany and France, and Microsoft itself do not convince you, I’m not sure there’s much else that will:
- The Chinese cyber attacks on Google (and at least 20 other large companies) got through because the exploited code worked only in IE6, on Windows 2000 and XP.
- The German and French governments have both asked its citizens to upgrade their IE6 browsers to prevent attacks happening to them.
- Microsoft released a security advisory warning against attacks specifically against Internet Explorer 6.
Mashable includes the three items above in its list, but the last one is the most compelling:
This will not be the last massive IE6 security breach: This flaw was unknown before Google’s groundbreaking China announcement. And it’s not the first flaw ever found with the browser — there are at least 142 vulnerabilities in IE6, 22 of which are not yet patched. Would you use armor that had 142 weak spots?
Internet Explorer 6 is a run-down browser with very little support for exploits. It’s more costly for businesses to leave it lying around like a ticking time bomb than exert effort to upgrade their systems.
The good news is, we’re getting bigger institutions stepping up against IE6. Let’s hope their spheres of influence really are that effective. You can’t get much bigger than European governments, Microsoft, or Google.

According to Ajaxian, the beloved tradition of learning by peeking at someone else’s source code is on the brink of extinction. Because Google is rewarding websites that load faster, people will stop at nothing to look good in the big G’s eyes, including code compression and more notably, obfuscation. This renders View Source useless.
While I feel it’s too early to call doomsday on View Source because of such speculation, like many I feel protective over it. It’s no surprise then that the Save View Source movement has been formed this early. The discussion is sparse, but Alex Russell elegantly explains why View Source matters, also reminding me why I love developing on the Web:
View-source provides a powerful catalyst to creating a culture of shared learning and learning-by-doing, which in turn helps formulate a mental model of the relationship between input and output faster. Web developers get started by taking some code, pasting it into a file, saving, loading it in a browser and hitting ctrl-r. Web developers switch between editor and browser between even the most minor changes. This is a stark contrast with technologies that impose a compilation step where the process of seeing what was done requires an intermediate step. In other words, immediacy of output helps build an understanding of how the system will behave, and ctrl-r becomes a seductive and productive way for developers to accelerate their learning in the copy-paste-tweak loop.
Even in compiling languages people learn better by looking at example code, but the culture of open learning can be felt strongest on the Web. Ajaxian posts a follow-up, in which I couldn’t agree more with this:
I personally feel like the ability to view source fit in perfectly with the culture of the Web, and was especially important early on. I am willing to bet that we have all learned from the notion of view source.
The freedom of access to tons of information on the Web is what it all boils down to. View Source is a sturdy consequence of that. It seems wrong to compare performance versus learning, but between those two, learning should prevail.
Then again, who can stand in the way of site owners desperate to turn up traffic and profit? Sounds like standards versus SEO all over again. What do you think—is the Save View Source movement an overreaction or a preemptive strike?

I’ll get straight to my answer: very.
More specifically, I’m quite excited about what this league is doing for a branch of typography which seems almost mythical. We know about paid fonts and free fonts, but what’s buzzing big right now is the use of fonts on the web with the emergence of @font-face embedding, webfonts, and services like TypeKit. But what about usage and modification of fonts in general?
The open source debate is always tricky when creative works are in question, but the case shouldn’t be different for typefaces. The League is going beyond that debate, but still has some tough questions to be answered:
Is open source typography important enough to fight for? Are we all brave enough to do something to change the status quo? Is the status quo okay, do we really need to change anything at all?
What is the status quo? If this 3-year old post is any indication, it looks like a sleepy town that needs some jazzing up. The Open Font Library is more closely linked to the open source software community than with the open source design community, but they mentioned Lettercase being a Github-like tool, so it looks like they’re taking steps towards that already.
Should we fight for open source typography and change the status quo? It could potentially compete alongside the hosted font embedding services and create a fine alternative for web designers using custom web fonts. Options are good.
Sound off with your thoughts there!
I started with this article about the decade that was in web design. (Note: an earlier version of this was done here.) It was not much more than a before and after look at the most popular websites out there. Of course, ten years is a long time in web design so the showcase is a satisfactory way to see how far we’ve come, but not quite enough. There was no discussion on the notable features from the different websites. We don’t redesign sites just because we want a different look, do we? We want them to improve. Answering how those sites improved over the years would be a worthy reference for all the web designers out there. This other one almost nails it, though it focuses on the business of these companies, not web design itself.
I hope the likes of Smashing Magazine or some fabulous curator of web design history would come up with an in-depth study illustrating how web design has evolved over the last ten years. Timelines like this and this could help with that, but still needs mention of developments like:
- the downfall of
<table> layouts in favor of semantic markup
- CSS sprites
- the growth of web typography, from sIFR to
@font-face
- Art Direction in web design
- mobile web design
- the HTML 5 Superfriends
- which website or company popularized which design pattern, from the glossy, candy-colored “Web 2.0 look” to the sleeker, more dramatic “Apple look” (though something tells me Apple is responsible for both)
Here’s another approach to the timeline, and is more of a Q&A over the years, and anybody can ask and answer. It also hasn’t been updated since ‘04, as it was part of the 2005 conference, A Decade of Web Design. Jakob Nielsen also did a backtrack that same year.
I’d also like to look forward. This prediction post is quite adequate (with pictures it would be perfect). I think this passage sums up what’s happened in the past decade and what will happen in the next:
While most these technological improvements tend to make the web a more and more homogenous place, at the same time, there is a tendency to create highly curated design setups that use different designs for each article.
There will always be a dichotomy between standardization and specialization on the Web but it’s only lately that we’ve been able to do so with less crap, more elegance. And I can’t wait to see how doing those two things evolve into even more exciting things in 2010 and beyond.
Need more crystal balls and time capsules? See also:
New year, new decade. But we still haven’t gotten past everything Web 2.0. We’re still dealing with the consequences of the social media revolution. The question is, which side are you on?
Pull the brakes?

We’ve seen people dumping Facebook and still not getting the Twitter mania, but here’s something pretty recent: the Web 2.0 Suicide Machine is making the meme rounds for those who suffer from social networking overexposure.
Most of the time we just hop on the bandwagon, publish the smallest details of our lives with abandon, and regret our actions only when it’s too late. Sites like My Parents Joined Facebook and Lamebook capitalize on those slip-ups, and we’ve all heard stories of people getting fired for something they posted online. A clean break from it all could be the answer. Or an exaggeration.
Interestingly though, Facebook has blocked the Suicide Machine. Thanks for playing!
Shift into high gear?

Tina Roth Eisenberg a.k.a. Swiss Miss tweeted that her unborn son already has a “gmail account, 3 domain names and a twitter account”. Pretty sweet, I’d say.
Again, this isn’t really a new phenomenon, but not many people are looking that far ahead. After all, who knows what the Web will be like in five to ten years. If domain names will still be the way to access websites.
Or maintain cruising speed?
Most of us probably lie in the middle and won’t think to axe their accounts or be so protective of their online identities as though they were real estate. Even if your new year’s resolution for social networking isn’t anything drastic, it’s still important to stay on top of your privacy concerns and online persona. Have you tweaked Facebook’s Privacy Settings yet? How about all the authorized third-party apps that have access to your Twitter account? Do you Google yourself every once in a while to see how other people find and paint a picture of you?
Bonus: try integrating a workout into those beloved websites. Now there’s a productive idea.