-
1
- #1
BillyRayPreachersSon
Programmer
As a result of doing more Firefox add-on development, I've become more aware of just how much most JavaScript code pollutes the global namespace.
I know it's over a year old now, but I've just found a handy tool to analyse the global namespace and see just how bad any pollution is.
As well as analysing your own scripts, it compares 30 or so of the most popular JavaScript frameworks to see just how bad their pollution is - some of them surprisingly bad (I'm pleased to see that jQuery scores fairly well).
It will also perform collision detection between the frameworks and your own code to flag any conflicts.
The tool is written by Mats Bryntse. You can read his blog post about the tool here and run the tool itself here.
All in all, a very handy tool!
Dan
Coedit Limited - Delivering standards compliant, accessible web solutions
Dan's Page [blue]@[/blue] Code Couch:
Code Couch Snippets & Info:
The Out Atheism Campaign
I know it's over a year old now, but I've just found a handy tool to analyse the global namespace and see just how bad any pollution is.
As well as analysing your own scripts, it compares 30 or so of the most popular JavaScript frameworks to see just how bad their pollution is - some of them surprisingly bad (I'm pleased to see that jQuery scores fairly well).
It will also perform collision detection between the frameworks and your own code to flag any conflicts.
The tool is written by Mats Bryntse. You can read his blog post about the tool here and run the tool itself here.
All in all, a very handy tool!
Dan
Coedit Limited - Delivering standards compliant, accessible web solutions
Dan's Page [blue]@[/blue] Code Couch:
Code Couch Snippets & Info:
The Out Atheism Campaign