3 ms·

>20 pricey smart JQuery guys See, this is how I knew you knew nothing about JavaScript. My bets, you're a manager that manages shitty Java coders who "used to

>20 pricey smart JQuery guys See, this is how I knew you knew nothing about JavaScript. My bets, you're a manager that manages shitty Java coders who "used to code" and is an obnoxious know-it-all. Scale of 1-10, how close am I? Edit: From your website: "currentlly: BofA" (sic). Feeling pretty warm on my bet so far.

mixitup12 14y ago
Like
- geuis 14y ago
  Write intelligent comments that advance the discussion in some way. This is not reddit.
  - joshmlewis 14y ago
    I don't even think that would fly on Reddit.
malandrew 14y ago
So so true. If you are hiring "pricey smart [sic] jQuery guys" then you're probably doing it wrong. You need to be looking for solid software engineers that know javascript well. If the developers you are hiring think (jQuery === javascript) and can't explain the difference between classical and prototypal inheritance , then you're screwed before you even begin.
- heretohelp 14y ago
  Good to know somebody understood what I was talking about. This is why I don't ask for a "jQuery" guy, I ask for a frontend engineer who's a solid programmer and likes working on interesting products.
  - cracell 14y ago
    I dislike the term frontend engineer or frontend anything because people use it to mean a whole range of things between JavaScript programmer, web designer, and HTML/CSS scripter. And while some people possess all three of those very different skills they are not at all the same thing.
    - deleted 14y ago
      [deleted]
- tmzt 14y ago
  Funny, the exact same question came up today. I'm curious what the actual difference between the two is as it's not apparent. (I use a mixture of function prototype with the extends pattern and CoffeScript which exports a function exporting a function.) From what I can see they behave the same as long as you follow the same pattern when writing a subclass.
  - johncoltrane 14y ago
    Prototypal inheritance is native to JavaScript while, simply because JS doesn't have classes, you have to go through quite a lot of troubles to make classical inheritance work.
  - malandrew 14y ago
    The main difference in many cases is memory usage. When cloning in prototypal inheritance, you point back to the prototype's function, unlike classical inheritance where you are copying methods on every instantiation.
krschultz 14y ago
I'm not happy that the top reply to the top comment on this post is a blatant ad hominem. What's your point about JavaScript?
- heretohelp 14y ago
  Apologies. I'm not happy that somebody who very evidently doesn't have a clue what they're talking about is the top comment. When people stop upvoting complete and utter tripe (which is nutritious btw), my response stops being necessary. I'd react the same way to any sort of ignorant pontification on clearly foreign (to them) material. Raise a fool on a litter and I'll tackle the people carrying the litter. I'm quite open to being proven wrong, but I don't expect to be.
  - bicknergseng 14y ago
    Ah. The "commenting to point out insanity upvotes by default" paradox. Quite ironic. Quite.

mixitup12 14y ago

geuis 14y ago
Write intelligent comments that advance the discussion in some way. This is not reddit.
- joshmlewis 14y ago
  I don't even think that would fly on Reddit.

malandrew 14y ago

So so true. If you are hiring "pricey smart [sic] jQuery guys" then you're probably doing it wrong. You need to be looking for solid software engineers that know javascript well. If the developers you are hiring think (jQuery === javascript) and can't explain the difference between classical and prototypal inheritance , then you're screwed before you even begin.

heretohelp 14y ago
Good to know somebody understood what I was talking about. This is why I don't ask for a "jQuery" guy, I ask for a frontend engineer who's a solid programmer and likes working on interesting products.
- cracell 14y ago
  I dislike the term frontend engineer or frontend anything because people use it to mean a whole range of things between JavaScript programmer, web designer, and HTML/CSS scripter. And while some people possess all three of those very different skills they are not at all the same thing.
  - deleted 14y ago
    [deleted]
tmzt 14y ago
Funny, the exact same question came up today. I'm curious what the actual difference between the two is as it's not apparent. (I use a mixture of function prototype with the extends pattern and CoffeScript which exports a function exporting a function.) From what I can see they behave the same as long as you follow the same pattern when writing a subclass.
- johncoltrane 14y ago
  Prototypal inheritance is native to JavaScript while, simply because JS doesn't have classes, you have to go through quite a lot of troubles to make classical inheritance work.
- malandrew 14y ago
  The main difference in many cases is memory usage. When cloning in prototypal inheritance, you point back to the prototype's function, unlike classical inheritance where you are copying methods on every instantiation.

krschultz 14y ago

I'm not happy that the top reply to the top comment on this post is a blatant ad hominem. What's your point about JavaScript?

heretohelp 14y ago
Apologies. I'm not happy that somebody who very evidently doesn't have a clue what they're talking about is the top comment. When people stop upvoting complete and utter tripe (which is nutritious btw), my response stops being necessary. I'd react the same way to any sort of ignorant pontification on clearly foreign (to them) material. Raise a fool on a litter and I'll tackle the people carrying the litter. I'm quite open to being proven wrong, but I don't expect to be.
- bicknergseng 14y ago
  Ah. The "commenting to point out insanity upvotes by default" paradox. Quite ironic. Quite.