3 ms·

Software development is a lot about making good use of resources and if you reinvent the wheel for every job you do, maybe it isn't your cup of tea. I've worke

Software development is a lot about making good use of resources and if you reinvent the wheel for every job you do, maybe it isn't your cup of tea. I've worked with developers who completely ignored good libraries and instead created their own terrible implementations. They got nothing done and what they did was a buggy mess that often needed months of patching. Finding a good middle ground is the best way to go and when the loading time increases by only a few milliseconds, but the development is a lot faster and cheaper, that's a good compromise in most cases.

posting2fast 8y ago
"friend to your coworkers, enemy to your craft"
austincheney 8y ago
Cliche ad nausium. It’s like saying I should never have to write my name more than once, because it is reinventing the wheel. In this case every call to the DOM goes from a slow baby crawl to rocket speed. In no other aspect of life do people make such empty excuses, using cliches no less, to intentionally remain in the stone age.
- talmand 8y ago
  Well, considering there are devices out there for the purpose of signing names repeatedly, I would say your example doesn't necessarily work. Totally depends on the situation. And why the assumption that modern versions of jQuery don't make use of modern DOM APIs?
  - austincheney 8y ago
    Here is what makes jQuery slow, both now and in the past: * querySelectors (standard or the home grown Sizzle engine) * Method chaining for trivial tasks, in many cases to compute data that is already statically present or directly assignable. Regardless of whether jQuery is using modern APIs or not there are old standards available, to JavaScript, that just about everything in jQuery eventually compiles down to. At the end of the day it becomes a matter of whether writing a couple of 3 line abstractions is far too hard of work or whether it is simply easier to push everything through 65k of jQuery purely for the sake of familiarity.

posting2fast 8y ago

"friend to your coworkers, enemy to your craft"

austincheney 8y ago

Cliche ad nausium. It’s like saying I should never have to write my name more than once, because it is reinventing the wheel. In this case every call to the DOM goes from a slow baby crawl to rocket speed. In no other aspect of life do people make such empty excuses, using cliches no less, to intentionally remain in the stone age.

talmand 8y ago
Well, considering there are devices out there for the purpose of signing names repeatedly, I would say your example doesn't necessarily work. Totally depends on the situation. And why the assumption that modern versions of jQuery don't make use of modern DOM APIs?
- austincheney 8y ago
  Here is what makes jQuery slow, both now and in the past: * querySelectors (standard or the home grown Sizzle engine) * Method chaining for trivial tasks, in many cases to compute data that is already statically present or directly assignable. Regardless of whether jQuery is using modern APIs or not there are old standards available, to JavaScript, that just about everything in jQuery eventually compiles down to. At the end of the day it becomes a matter of whether writing a couple of 3 line abstractions is far too hard of work or whether it is simply easier to push everything through 65k of jQuery purely for the sake of familiarity.