Bad, Bad Programmer

After just watching Chrome (Windows OS) hover at over 90% of my CPU (with only one tab open Jesse), and routinely seeing a few tabs in Firefox kill my other (Ubuntu OS) system's resources - while at other times I can sail along fine with absurd amounts of windows and tabs open - I realized, it's just bad programming.

No, I'm not blaming the developers of the popular (and even unpopular) web browsers - they deserve a pat on the back for how robust their code and rendering needs to be (except when they break standards on purpose - bad Microsoft). It's the guy who goes to client meetings in a tee shirt and jeans, calls himself a 'designer', then tells the client that he knows javascript just because he's heard of this 'prototype thing' that he downloaded yesterday.

I blame him.

Used to be that 'programming' was done by that guy over there. You didn't know what he did, or how he did it, just that he could take those 53 steps you went through every month and give you a program that did it all for you. And better than you could do. He was 'the sorcerer'. You needed something done, you went to him.

It's not like that anymore. With every new browser, with every step of web computing, more and more is demanded from what started simply as way to format text documents. Now, thanks to web 2.0, cloud computing, and ajax, that guy in the tee shirt is running programs on your computer every day, and he can't even correctly close a link tag without dreamweaver.

Every time I visit a site, I'm potentially allowing horribly written code to run on my computer. I'm not downloading anything, I'm not installing anything, I'm just following a link. And I can only hope that my browser is smart enough to kill that code before it's killed by that code.

The problem with the new era of web centric computing? It's that everyone can be a programmer. And that's not good.

Tim Lytle [02/17/09 17:38:37] | 0 Comments | Stream