Posts Tagged ‘sitepoint’

Comic Update: I’m With Squirrel

Monday, January 18th, 2010

Today’s comic does not precisely plumb the depths of the web standards world. There’s no CSS compatibility joke, no HTML5 politics, and not even a dig at Opera. Which, I know, is a major drag for you all.

It serves two purposes. The first is to look back at the fun I had participating in SitePoint’s podcast “HTML5 is a (Beautiful) Mess“, and pay homage to the gentlemen I had the pleasure to speak with: Canadian Kevin Yank (as one of the fellow speakers put it, is there a Kevin Canuk in the US somewhere?) and Brits Ian Lloyd & Bruce Lawson. Such fun, idyllic moments like debating HTML5′s wrecked politics are too delightful to go unchronicled.

The other purpose relates to Kevin’s first joke in the podcast. He asserts (falsely) that we’ve gathered to discuss the recent troubles plaguing NBC’s late night line up, in particular the Leno vs O’Brien issues of the Tonight Show. This joke threw Ian and Bruce, who aren’t plagued daily with American late night talk shows, but it sparked in me the remembrance of a tweet I once received from one @GeekGamerGirl that made my heart sparkle: CSSquirrel is The Daily Show for web designers. Don’t stop, we need you to make up for all the bitchy little girls out there.

So today’s comic is more of an announcement. 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.

So, screw Leno or Coco. I’m with Squirrel. (For those who miss the reference in the last panel, it’s a play on the “I’m With Coco” badge by artist Mike Mitchell).

Yes, the shameless self-promotion is concluded. Enjoy your day.

The Squirrel in Crisp Audio! SitePoint podcast “HTML5 is a beautiful mess”

Friday, January 15th, 2010

On Wednesday I had the honor and pleasure of participating in a podcast recording session with HTML5 Doctor Bruce Lawson, Beginning Web Design author Ian Lloyd, and SitePoint’s Kevin Yank in a discussion about HTML5, and whether it’s just exploded over all our face.

The end product, “HTML5 is a beautiful mess” is now up at SitePoint. I’d be tickled pink if you took the time to listen.

As you may recall, I discussed ranted about this subject on Monday with the strip The HTML5 Show (AKA a Mess) and the related post.

Mostly, HTML5′s a mess in the political sense. The organizations behind it (W3C and WHATWG) are increasingly in conflict with one another. Additionally, in my opinion, Ian Hickson is increasingly disregarding any attempt at a legitimate process and simply putting what he pleases in the spec, as he pleases.

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.

If I have one beef with the whole podcast, it’s the fact that I’m talking with a pair of Brits. Which, as every movie-going American knows, instantly sound more clever due to their crisp accents. Also, if the transcript is any guide, my sentences tend to roll off the rail quite a bit, inflicting casualties to adherents to the English language.

So, if you have the time, please go have a listen, and then please come on back here and post any thoughts you had at my butchery of verbs, the points that the participants brought up (or even better, the points we didn’t) and how lovely Bruce Lawson’s voice is.

Comic Update: This is not a Reference

Monday, July 13th, 2009

[Update: The CSS3 Attribute Selectors article in the Reference was updated just prior to this post going live. So my ranting about that section is largely out-of-date and can be summed up now as "Took much longer than I'd anticipated".]

When I was first hired by Mindfly in 2007 I was not what you’d call “web standards aware”. Upon seeing the table-based layouts, font tags, and massive collection of inline-styles that stampeded through my pages like wild buffalo, grown men would gnash their teeth and wail in torment and mothers would hide their children.

It only took a few crying infants for me to realize something needed to change if I wanted to keep this career. My infovore nature led me to consume as much information on the topic I could muster, starting with Andy Clarke’s Transcending CSS and continuing through dozens of online tutorials and references. Learning the errors of my past, I spent a bit of time quietly taking my old sites out to the woods, instructing them to dig their own graves, then whacking them with a shovel before burying them for all time.

After the evidence had been destroyed, I went about trying to make compliant, pretty sites using the best practices in HTML and CSS. By 2008, I had friends who thought making website was the bee’s knees, but they didn’t know where to look for learning CSS, etc. At that point my bookmarks of handy sites had grown enormously, so I heartily recommended several.

One that I mentioned time and again was the Sitepoint CSS Reference, which was (to my knowledge at the time) a very complete, useful reference to the wonderful world of CSS. It even included tasty tidbits about CSS3 support. The main reason I sent each person who asked to this reference was explained in Sitepoint’s announcement“…the reference contains a bunch of features that make it stand out from the pack — things like cross-browser compatibility charts and user feedback to ensure that it is accurate, up to date, and best-practice. If you’re building sites with CSS, this is a reference you’ll keep coming back to again and again.”

With the speed at which this industry changes, who wouldn’t want access to a constantly updated reference that even incorporated outside feedback?

There is a problem, unfortunately. As near as I can tell, the reference isn’t updating. Since its launch, it seems to be sitting still, failing to modernize its information as browsers march on. Every single browser on their compatibility list has had major updates since its launch, putting much of the CSS3 support information well out of date. Never mind that Google Chrome has been out for quite a bit of time now (as the Internet sees such things) and has no compatibility information present despite it’s higher browser share than Opera in most markets.

In a book, this situation is a necessary reality. Books, by their static nature, are out-of-date typically before they’ve even been published, requiring later editions, etc. But for a web-based reference, which claims specifically to have the benefit of staying up-to-date and incorporating user feedback, this isn’t terribly cool.

For me, the situation is exasperated by their promise to incorporate feedback (or even claiming to do so) when they (at least in situations I’ve experienced) clearly are not. To back my claim, I’d like like to direct you to my own experience I’ve had, which I’ll call Exhibit A. If you examine the page on CSS3 Attribute Selectors, you’ll find that it erroneously claims that Internet Explorer 7 completely fails to support these little gems.

I’m no IE fan, but I can tell you my friends, that this is a falsehood. And because I was foolish enough to take that advice at face value (who doesn’t trust Sitepoint?) I created IE-specific workarounds in a project where I first included these selectors, workarounds which ended up costing me a decent chunk of time. It was only later that I decided the best experience is personal experience and I actually tried the selectors in IE7, only to discover that they work perfectly fine. I’d wasted time (translate that: money) fixing a nonexistent problem they claimed existed.

Not being the type to hoard information, I shared the fact that they were mistaken in a comment on May 2, 2008, complete with a link to a test page to confirm that I wasn’t full of hot air. (The old test page has disappeared, so you can see what I’m talking about if you check this test page in IE7). Eventually they marked that they’d incorporated my comment into the article… only they hadn’t. It still incorrectly stated IE7 support didn’t exist. Sometime much later (aka, this year), I commented in annoyance at the mistake again on Twitter. They responded multiple times over Twitter to me, asking for clarification (which I gave) and then promised to update their Reference (which they didn’t).

That was a couple months ago.

Today’s comic shares my view on the so-called Reference, albeit in a somewhat abstract sense. So let me make it clear: I don’t think the Reference is what they claim: a reference. Rather, much like René Magritte’s unpipe it is not what it appears, merely the image of it. The unreference, if you will, is something that claims authority and completeness but increasingly lacks both as time moves forward.

One erroneous page isn’t worth tearing down their entire reference. However, with a complete lack of modern CSS support information on every major browser, Sitepoint’s “up-to-date” CSS Reference has become largely useless as a source for web designers living and working in 2009.  I’m upset at this, because I sent literally everyone I knew with an interest in learning CSS to their site, saying “Hey, these guys know their stuff.”

Now… well, now I tell people to avoid it. I’ll repeat that for anyone reading: Don’t bother. They mean well, but they’ve failed to live up to their mandate of keeping updated. In March, when I’d commented (again) on my disgruntlement with the lack of updates, I received the following pair of tweets from Kevin Yank (@sentience).

April 6, 2009 4:19pm: “What erroneous compatibility info did you find? We are planning to refresh the Reference for the latest crop of browsers in May.” (after which I gave a summary).

April 6, 2009 4:50pm: “Thanks! Will get that corrected ASAP.

It’s July now. I think we may have different definitions for “corrected” or “ASAP”.

CSS3 Attribute Selectors: So Hot Right Now

Thursday, May 1st, 2008

As discussed here, I’m really getting into CSS3 Attribute Selectors. As mentioned earlier in my Yo-Yo post, I’ve been looking into solutions to make these guys more accessible, and I’ve come full circle to realize that I don’t need to do anything extra to incorporate them in my website and have users see them in any major browser. This is because:

1. The modern versions of Internet Explorer, Firefox, Safari, and Opera all support them. (Here’s a test page at Mindfly‘s website to prove the point).

2. The Dean Edwards IE7 script DOES extend full CSS3 attribute selector support to IE6 (I’m guessing my earlier tests had an error, because now I’m showing full compliance with this second test page that includes that script (once again, at Mindfly).

The CSS3 features I’m really looking for support for now, then, are the CSS3 pseudoclasses and multiple background images. *drool* Multiple background images alone would help cut down on my markup immensely, making features such as rounded boxes so much less of a pain in the arse.