A while ago I wrote about why javascript libraries are not necessarily helpful in my line of work (namely because of their high potential for abuse). Just now I stumbled upon another problem that makes them even less useful for me.

A javascript lib provides – in theory – a common framework to write reusable and exchangeable modules and widgets that can be distributed over the web and plugged into existing applications. After all we all use a common code base, so there is no room for conflicts, or is there.

Actually there is. Today the attempt to use three different prototype based widgets (and the subsequent attempt to find replacements) landed me right in version hell. Evidently every prototype based snippet uses a different version of the lib and backwards compatibilty, if at all intended by the prototype makers, is extremly limited. I’m not sure that it is actually faster if I write the required functions myself, but I bet it’s a lot less frustrating.

And while I’m at it, here’s a heartfelt “Fuck you!” to all you browser manufacturers out there. I don’t know if you know how much unpaid overtime your crappy software causes for people like me, but my guess is you know it and break things on purpose. Oh well, who needs sleep anyway.