From: Garrett Smith on
I interpret this question as:

"I want to call the dollar function. How can I know what it will do?"

http://stackoverflow.com/questions/2754818/how-to-detect-what-library-is-behind-the-function
--
Garrett
comp.lang.javascript FAQ: http://jibbering.com/faq/
From: David Mark on
Garrett Smith wrote:
> I interpret this question as:
>
> "I want to call the dollar function. How can I know what it will do?"
>
> http://stackoverflow.com/questions/2754818/how-to-detect-what-library-is-behind-the-function
>

Too bad the jQuery, Prototype, etc. people didn't think about how stupid
it is for all of the GP libraries to use the same symbol. All of that
talk about "namespaces" and "unobtrusiveness", six billion possible
variable names and those morons still managed to crash into each other.

And some idiot on that same site once told me that it was "naive" to
overwrite the $ without "checking it" first. And if it is there...?
From: "Michael Haufe ("TNO")" on
On May 2, 5:13 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote:
> I interpret this question as:
>
> "I want to call the dollar function. How can I know what it will do?"
>
> http://stackoverflow.com/questions/2754818/how-to-detect-what-library...

This is wrong on so many levels I don't even know where to begin. I
guess the proper response is "Mu".
From: David Mark on
Michael Haufe ("TNO") wrote:
> On May 2, 5:13 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote:
>> I interpret this question as:
>>
>> "I want to call the dollar function. How can I know what it will do?"
>>
>> http://stackoverflow.com/questions/2754818/how-to-detect-what-library...
>
> This is wrong on so many levels I don't even know where to begin. I
> guess the proper response is "Mu".

Yes, as is often the case on that site (with regard to JS anyway), it is
a silly question followed by a stream of even sillier answers. The only
right answer for the OP is to stop and think about what they are doing.

The latest answer contains this howler:-

"Seriously, isn't one of the main points of these library to avoid
having to write three different variations of each line of code for each
browser?"

That may well be what John Resig and the Prototype people thought they
were doing. But then _they_ ended up writing three lines of code for
each browser (the ones they had heard of). Then I had to go and tell
them there was a fourth. :)

http://groups.google.com/group/comp.lang.javascript/browse_thread/thread/415949d1bcce6e6a/03c4d326340e7f7d?#03c4d326340e7f7d

Their solution has been to decide that they don't "care" about any
browsers more than a year old (or anything with less than 1% of the
world using it). That's pretty telling of their cross-browser success
(or lack thereof). More telling is that apparently "VK" endorses such
"strategies". That's worse than bad company.

Conscientious customer: "Hey, your site doesn't work in my browser"
Clueless developer: "You've got the wrong browser according to John
Resig. And he's a Ninja."
Conscientious customer: #$!@# *click*
From: "Michael Haufe ("TNO")" on
On May 2, 8:13 pm, David Mark <dmark.cins...(a)gmail.com> wrote:

> Their solution has been to decide that they don't "care" about any
> browsers more than a year old (or anything with less than 1% of the
> world using it).  That's pretty telling of their cross-browser success
> (or lack thereof).  More telling is that apparently "VK" endorses such
> "strategies".  That's worse than bad company.

For a general purpose library I can understand the argument against
supporting a browser with a market share of less than 1% _IF_ given
that the alternative inflates your code size by 20% (arbitrary big
number) such as NS4 or IE versions below 5.5 and that the browser
share is in decline.