Re: "The Good Enough Revolution" - As it applies to js
- From: Erik Reppen <erik.reppen@xxxxxxxxx>
- Date: Mon, 31 Aug 2009 11:30:31 -0700 (PDT)
And certainly a "good enough" philosophy should be challenged at every
opportunity. At the least, the goal should be the best quality
possible within the project's constraints (where quality is judged on
functional performance, not things like crappy UI effects).
--
Rob
My experience is that I have not ended up writing JQuery instead of
JavaScript. It's a really fancy object that takes a lot of the time
and tedium out of the DOM API and uneven support for it. It gets heavy
use but not exclusive use. There's a kind of an absolutist philosophy
here on things. Yes, it uses browser sniffing for some things. I don't
know where yet, but I've read enough of Resig's stuff to trust he's a
good enough dev to avoid it when possible, but sometimes what we're
anticipating is more than just whether a given method or property
exists. How do you test for whether the box model is completely hosed,
for instance? There is more to the unique quirks of a browser that
could be relevant to a library than just the JavaScript methods and
properties supported and I'm a strong believer that coding for the web
requires a strong understanding of the relationship between the JS and
the other languages it's typically intermingled with. Too many would-
be JS rockstars don't know jack about CSS or the finer points of HTML
and their code suffers for it.
On your final point, I agree. I don't think I need to justify the use
of a library as a 'good enough' policy. If a library helps me do
better work in the time allotted, it doesn't murder performance, and
seems perfectly stable to me, I'm going to call that a major win, not
a compromise. There's nothing about extending the element object with
a whole bunch of methods using prototype in a way that doesn't
interfere with the core language that isn't JavaScript. That sort of
flexibility is one of the things that makes JS a beautiful language to
work with.
There is nothing we can do about people who don't want to learn the
craft properly. They are going to produce crappy code regardless of
whether they're pulling it from an ugly library, Dynamic Drive, .NET,
or writing 800-hose hosebeasts all by themselves. Bloat is inevitable
with standards as low as they are to people who don't know better and
good devs tend to eschew management in favor of continuing to actively
write code so that's not likely to improve. If the amateurs do
horrible things with JQuery, let them, or help them along however you
can. Just be happy that there's enough of them out there to keep
anybody with more than mediocre skills in demand. The more they fail,
the stronger arguments for doing it right become. And the more people
who belong there are relegated to Craigslist Computer Services section
offering web services 'any way u want it.'
.
- References:
- "The Good Enough Revolution" - As it applies to js
- From: Matt Kruse
- Re: "The Good Enough Revolution" - As it applies to js
- From: RobG
- Re: "The Good Enough Revolution" - As it applies to js
- From: Pherdnut
- Re: "The Good Enough Revolution" - As it applies to js
- From: RobG
- "The Good Enough Revolution" - As it applies to js
- Prev by Date: ♂⊙√⌒Paypal paymen Wholesale Cheap Boots brand shoes ( www.salewto.com ）
- Next by Date: Re: "The Good Enough Revolution" - As it applies to js
- Previous by thread: Re: "The Good Enough Revolution" - As it applies to js
- Next by thread: Re: "The Good Enough Revolution" - As it applies to js
- Index(es):
Relevant Pages
|
Loading
