critical resolution
There is something to be said for making resolutions. I don’t necessarily attach these to a particular time of the year or particularly special occasion, but I do make them. Resolutions help you grow, right? At least, that’s the intention.
There has been an interesting buzz trending around the internet, for the past few weeks, that shouldn’t go unmentioned. The buzz word in this trend is critique. Whether it’s criticizing ourselves, criticizing others or criticizing how others are criticizing us, the venom is in the air. ‘Tis the season, right?
I think critique is healthy. It can be a method by which to grow, much the same as a resolution. In fact, at best, healthy critique can lead to thinking, reflection and ultimately resolution.
On December 13th, Andy Clarke stirred up the bees’ nest by calling for a disbanding of the CSS Working Group. Two days later Jeffrey Zeldman responded to Andy’s rally, with rather harsh criticism.
…Proposing change because you are disappointed and frustrated isn’t good enough. Anger can be brilliantly motivating; but anger is not a strategy.
Many others chimed in and virtually tore Andy a new one. So this, we find ourselves at a crossroads. Will this upheaval turn over fresh enthusiasm or will wounded soldiers turn away from each other, with hands stuffed in pockets?
One of Andy’s most inflated critics was Daniel Glazman, who went on to say:
…What do you think is a standardization body ? It’s a BATTLEFIELD where vendors fight for competitive advantage…
Actually, I think that was Andy’s point. That is NOT what a standardization body should be! We, as a community of developers are not pushing for standardization so that private companies can have a competitive advantage! That, in part is what we are trying to avoid. But again, this discourse was all very good. Angry, pissed off, frustrated et al., the discourse was happening. The test, in my eyes, was to see how was how Andy would respond.
I have a background in art. I know criticism. I can be a ripe asshole at times, but I can also take as well as I can give. Andy handled the attacks well and elaborated on his earlier, more top-off rant, with clarity.
There are two possible things I see coming out of this. One - A split. Developers against developers. A divide and conquer strategy that could prove valuable to proprietary browser companies. Two - A new found commitment and passion. An opening of communication channels between website developers and browser programmers.
Rivalry is in the blood of all developers. A strong belief in what you know, is part of what makes us do what we do. But, in all of this, it is important to remember pecking order. We don’t make websites so that web browsers have a purpose in life. And browser developers don’t make web browsers so that our websites have a place to live. As developers on both sides, we have the same goals. We can be pushed and pulled, but should always remember that.
I’m off to board a plane to New York. Wishing everyone the best for the new year.
