Print

Print


Disclaimer: I'm a prototype / scriptaculous / lowpro junkie.

My big caution with all of these frameworks is the same as... well,
the caution you get whenever moving to a technology with a higher
level of abstraction: it doesn't totally save you from knowing about
the underlying tech. If you don't know how XmlHTTPRequest (or DOM
manipulation or events or javascript's peculiar object model)
*works*, then going beyond what the libraries give you for free is
gonna be hard.

That being said... if you try to write your own cross-browser event
code today, you are a fool ;-)

I *heartily* recommend source diving in these libraries. Seeing how
experts code js has been immensely helpful for me -- just as crawling
through ActiveRecord has been invaluable in learning ruby.

-Nate

On Nov 29, 2007, at 10:33 AM, Keith Jenkins wrote:

> jQuery++
>
> I like to do things from scratch, but have never regretted moving to
> jQuery.  Whatever time it takes you to check it out will be paid back
> a thousand times, at least.
>
> Keith
>
>
> On 11/29/07, Ewout Van Troostenberghe <[log in to unmask]> wrote:
>> To point out why the use of a Javascript framework is important,
>> let me
>> put your code into jQuery (http://jquery.com)
>>
>> $.get('index.cgi', {cmd:'add_tag', username:'username'}, function
>> (html) {
>>   // do whatever you want here
>> })
>