Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #7981

Re: jQuery takes down the Guardian

From David Mark <dmark.cinsoft@gmail.com>
Newsgroups comp.lang.javascript
Subject Re: jQuery takes down the Guardian
Date 2011-11-04 03:37 -0700
Organization http://groups.google.com
Message-ID <02f18aae-2192-4da2-a8b0-191179dbdea7@o19g2000vbk.googlegroups.com> (permalink)
References <32fd8b28-5e5b-4d8e-818b-49b12ccdac2b@a7g2000yqd.googlegroups.com> <QvmdndCMJ8p22S7TnZ2dnUVZ_rKdnZ2d@westnet.com.au>

Show all headers | View raw


On Nov 3, 9:50 pm, Andrew Poulos <ap_p...@hotmail.com> wrote:
> On 4/11/2011 6:52 AM, David Mark wrote:
>
> > Nah, those fabled attr issues don't cause problems in the "real
> > world".
>
> >http://www.guardian.co.uk/info/developer-blog/2011/nov/03/javascript-...
>
> The issue would be no different to a lead developer changing a feature
> of some custom js code a project ran on and failed to document it
> properly, or that those underneath her didn't understand js well enough.

Sort of. The problem is that Web developers abdicate responsibility to
"lead developers" that they don't know. Their only documentation is
the jQuery documentation, which is rubbish. For years, the "attr"
function has been documented to get/set attributes, but it never did
that at all (except when it "detected" an XML DOM). The well-
documented boondoggle with jQuery 1.6 was the result of changing the
method to match the name/documentation (and never mind that it broke
thousands of extant apps). Then they put it back the way it used to be
on the next release. They are just going around in circles.

>
> To be fair, even though they don't understand the issues they were able
> to fix it pretty quickly (in that they were able to get their site
> working "properly"). The next time they'll just test first before they
> deploy.

What they did is the standard mystical incantation: rearranging
patterns of code until they seem to work. Ultimately, they settled on
using the "removeAttr" method, which was the centerpiece of my last
jQuery review. For those who missed it, that method is confused
nonsense as well (and changes periodically as their "test-driven"
knowledge gathering reveals more cracks in their assumptions). If only
they would RTFM, they wouldn't be causing so much confusion among
beginners who rely on their "expertise" to keep them out of trouble.

Back to comp.lang.javascript | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

jQuery takes down the Guardian David Mark <dmark.cinsoft@gmail.com> - 2011-11-03 12:52 -0700
  Re: jQuery takes down the Guardian RobG <rgqld@iinet.net.au> - 2011-11-03 13:56 -0700
    Re: jQuery takes down the Guardian Matt McDonald <matt@fortybelow.ca> - 2011-11-03 15:47 -0600
      Re: jQuery takes down the Guardian Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-11-04 00:24 +0100
      Re: jQuery takes down the Guardian RobG <rgqld@iinet.net.au> - 2011-11-03 16:30 -0700
        Re: jQuery takes down the Guardian Matt McDonald <matt@fortybelow.ca> - 2011-11-03 19:16 -0600
          Re: jQuery takes down the Guardian Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-11-04 11:05 +0100
          Re: jQuery takes down the Guardian Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2011-11-04 13:25 +0100
            Re: jQuery takes down the Guardian Denis McMahon <denismfmcmahon@gmail.com> - 2011-11-04 15:33 +0000
    Re: jQuery takes down the Guardian "J.R." <groups_jr-1@yahoo.com.br> - 2011-11-03 22:42 -0200
  Re: jQuery takes down the Guardian Andrew Poulos <ap_prog@hotmail.com> - 2011-11-04 12:50 +1100
    Re: jQuery takes down the Guardian David Mark <dmark.cinsoft@gmail.com> - 2011-11-04 03:37 -0700
  Re: jQuery takes down the Guardian "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2011-11-05 07:36 -0700

csiph-web