4 ms·
I'm a little confused here. First, let me echo my sibling comment by saying that, yes, $ is a function, but no, the name "$var" will not execute the $ function.
by pmichaud 17y ago
I'm a little confused here. First, let me echo my sibling comment by saying that, yes, $ is a function, but no, the name "$var" will not execute the $ function. To me it's a method of notation, as the sibling also said.
But you seem to understand that point, so I'm confused why you said what you said.
You're saying using $ as notation might confuse people new to jQuery and presumably javascript, who might not realize that $ is a function. You're saying that they would or might therefore conflate $var with $('selector'), leading to inefficient code?
So, I should abandon a concise convention because a tiny subset of the programmer population might misinterpret a detail of my code, causing them to implement superficially similar code in an inefficient way? Is this a problem you run into a lot?
- axod 17y agoI'm saying that using $ to name a function, isn't a good idea. It looks cheap to use, but it's not. That's my point. Same reason I hate those things in C# is it? where you can get some code to run each time a variable is read/written to.
- pmichaud 17y agoProperties. Properties make for some mighty clean code though. I guess you have a particular bias toward protecting systems from crap programmers, which may serve you well in your environment. In my environment being concise wins because no one is an amateur.
- axod 17y agoNot really. I'm a sole developer at the moment, so I value efficient easy to read code. Mainly a matter of taste though I expect.