Tuesday, September 12th, 2006
Web Development Tools for the Power Developer
Category: JavaScript
, Utility
Brennan Stehling has done a nice job in compiling Web Development Tools for the Power Developer:
Validators
Javascript
Websites
- A List Apart
- Position Is Everything
- Quirks Mode
- WaSP
- CSS Zen Garden
- CSS Crib Sheet
- Yahoo! Browser Grade Chart
ASP.NET
- Atlas Toolkit
- Web Application Projects
- Web Deployment Projects
- CSS Control Adapters
- Web Development Helper
- Script#
- CSS Properties Window
- Scott Guthrie’s Blog
- Nikhil Kothari’s Blog
Proxy Tools
A lot of these have been discussed a lot, and are familiar to our readers, but it is always good to take another look at the list.
3.4 rating from 31 votes
I wouldn’t say he did a “nice job”, he forgot FireBug, the most important one of all.
And mootools?
I’m surprised that the JQuery evangelists haven’t jumped on this like a pack of wild dogs. :) Me…. I’m a Prototype/Scriptaculous user myself. I’m coining an easier term to for the pair here “Protaculous”.
Come on, he missed the two most essentials tools of all: FireBug and the Web Developer Toolbar…
And it would have been worth mentioning that there is a Web Developer Toolbar for IE as well (even if it is a rip off its useful from time to time) and that the Webkit nightlies now also haved an awesome DOM inspector as well as a JavaScript Debugger.
Let alone at least 10 other useful Firefox extensions, like IEWatch, CSSViewer, LiveHttpHeaders, …
Don’t forget jQuery (www.jquery.com) by the Javascript list.
and where was lost Google Web Toolkit (GWT)
I think “Power Developer” often doesn’t use third part libraries (prototype or scriptacolous are really cool but not indispensable, imho) but creates His “wonderfull” libraries :) … and a Power Developer should use FireFox with FireBug as Web Developer Toolbar too and maybe other usefull extensions.
Finally, I think a JavaScript Power Developer should use a “lightweight-low-level-library” to develop His simple, medium or complex libraries/applications using standard JavaScript 1.6 (at least) code compatible with “every” browser to reduce size of global libraries/scripts and to write code “once for all” using last Array, Function, String or Object proto
[spot?]
…. then I think JSL should be present on JS list :P (and maybe other “low-level-libs”)
[/spot]
Yes I must agreee this list is far from a “nice job”. Of all the developer tools that were left out, I think it is a crime to over-look Browsr Camp. For a lot of people it is difficult to have a system with every browser under the sun installed — this makes Browsr Camp a very useful tool indeed:
http://www.browsrcamp.com
As bob said, FireBug extension is definitely my weapon of choice to understand what’s going on while developing Ajax base web applications.
A list of all the browsers that require supporting would be good to scare a few people too! :)
[...] Then there is ajaxian who has a nice list of tools for ASP.NET developers. Just in case, not everybody can afford to hate and dismiss Microsoft, so it’s nice to see a BLOG with hands-on information for those of us who still plan on delivering to a number of operating systems and web browsers. Aside from covering IE7–related issues and AJAX by-and-large, the ajaxian also covers a lot of good information for those of us who still believe in JavaScript and all the good things it does. [...]
+1 for where the he** is firebug? If there are any essential tools for web development, firebug has to be near the top of the list.
New unobtrusive lib on the track http://rajeshanbiah.blogspot.com/2006/09/behaviorsjs-alternative-to-behaviourjs.html ?
blowjob
cefnfbhc gkfzyaitwk rswkjwa
[...] Ajaxian » Web Development Tools for the Power Developer (tags: javascript javascriptpoweruser) [...]
I just wish there was one standard across the board for mobile devices or that all devices that view the web (mobile or otherwise) conform to these standards so I dont have to have iexplore/firefox/safari/opera/iphone/wap versions of pages to make them look correct.