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?
Right now I’m listening to a live piano performance by Imogen Heap (she calls it “piano noodlings”) being broadcast over USTREAM, announced over Twitter a few minutes ago.
Several hundred other people are watching too, and it’s a new kind of musical experience thanks to the real-time Web. People have spoken of it before, and this is a fascinating aspect of it.
We can all sit down in front of the computer in our individual homes and listen to an Imogen Heap concert, live, together. It’s not quite the real thing, of course, but it’s different. Good different. It’s simple, spontaneous, and inclusive.
I can’t wait to see what other artists and other game-changers come up with in this next era of the Web.
You can never run out of things to talk about when it comes to cascading style sheets or CSS, but lately there have been developments that are more than worth your while. CSS3 is slowly but surely becoming mainstream thanks to several browser updates, while the gurus continue to think up smart ways to code those stylesheets.
Update: Ajaxian blogs that WebKit will support CSS variables. Amazing news that has come out just in time with this blog post. I’ve listed it below as well.
Tools and Frameworks
I’m not going to mention every imaginable CSS framework and piece of software out there, but these are worth looking at.
Stylizer: Skybound Software comes out with perhaps one of the most interesting (read: intuitive) CSS editors to date. It helps that it has a free version with a 14-day trial for its Ultimate counterpart.
YAML: Smashing Magazine shows how it is possible to create a flexible layout using Dirk Jesse’s HTML/CSS framework called YAML. The YAML Builder is an excellent plus.
CSS Cacheer: Shaun Inman releases a mini-application for CSS caching.
Best Practices
Here are some great nuggets of advice that will help guide you when writing your own CSS.
Font Stacks: The Unit Interactive blog lists various scenarios in which you should order your CSS font stacks. A PDF file is available for download, too.
Fun With Floating in the Grid: Devlounge recommends several practical CSS classes and layout techniques to achieve hassle-free floats and grids.
Performance Testing: jpsykes reports how the different browsers fare using different CSS selectors and attributes.
Faux Absolute Positioning: A List Apart comes up with a new layout technique that does away with hacks.
Nesting Specifics: DZone goes into the nuances of CSS selector specificity.
CSS3 and Beyond
If you’re still hesitant to use CSS3, you might change your mind now that some of the most popular browsers are slowly incorporating support for it.
Firefox 3: Killian Valkhof and David Baron write about support for several CSS3 features in the latest version of Mozilla Firefox. These include ligatures, kerning, font-size-adjust, inline-block/inline-table, and even text-shadow—coming in Firefox 3.1. The complete list is on Mozilla’s official page.
Opera 9.5: The Opera Developer Community discusses the CSS3 features its own browser supports, namely, @media, text-shadow, opacity, HSL values, overflow-x/overflow-y, :firstof-type, :nthchild, -o-background-size. Not to mention HTML 5 elements and SVG. Don’t forget to check out Opera’s debugging tool, Dragonfly.
Safari 3 has been out for a while now, but it’s Internet Explorer that we’re really waiting for. Unfortunately, IE8 will continue to lag behind.
Qualified Selectors: Shaun Inman proposes a different breed of CSS selectors.
CSS Variables: David Hyatt announces that WebKit now supports CSS variables as documented here.
