Well, as I've put it down below, this isn't really an issue of code 
purity (although I'm sure that bugs me too).  What I was trying to say 
was that it is an issue of readability.  At least to me, seeing $ in my 
javascript code indicates DOM manipulation.  So my preference is to make 
anything not pertaining to DOM manipulation not look like jQuery.  I 
certainly wouldn't have any issues if John or the jQ community wanted to 
write/sponsor/host solutions that didn't fall under the jQ mandate, but 
what harm is there in putting them into their own namespace?  I'd argue 
that it would only add clarity to the situation.  jQuery remains 
coherent and quantifiable, rather than an ever expanding kitchen sink, 
and we get peer libraries that the community knows will play well with 
the beloved jQ.  Remember the old Unix saw about doing one thing and 
doing it well (aside from Emacs, of course).  I think it ought to 
pertain here as well.

-Stephen


Dan Atkinson wrote:
> I'd be -for- having something like this inside jQuery.
>
> For all the other non-element additions that there in jQuery, something like
> this would be a great feature to have.
>
> As much as code purity is a good thing, there comes a point when you say
> 'well, this might just make things better...'.
>
>
> Stephen Howard wrote:
>   
>>
>> Christof Donat wrote:
>>     
>>> Cons:
>>> - either you need to do synchronous loading like JSON does or you need to
>>> work 
>>> with callbacks as I do. Synchronous loading blocks the browser, callbacks
>>> are 
>>> not understood by everyone.
>>>
>>>   
>>>       
>> I believe Christof is referring here to JSAN (openjsan.org) not JSON 
>> (data format) when he is referring to the synchronous loading
>>
>>
>> I'd like to throw in my voice in support of Christof's call for keeping 
>> things like this out of jQuery proper.  To me 'doing different things 
>> should look different'.  When i see raw ajax calls and such hanging off 
>> $ that looks wrong, as I think of $ signifying that I'm selecting and 
>> manipulating the DOM.  If I'm doing something that doesn't have to do 
>> with DOM selection, I shouldn't see the $ in my code, because that's 
>> what I associate it with, and anything else interrupts the visual 
>> texture of my code.
>>
>> -Stephen
>>
>> _______________________________________________
>> jQuery mailing list
>> [email protected]
>> http://jquery.com/discuss/
>>
>>
>>     
>
>   

_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to