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

Groups > comp.lang.javascript > #15102

Re: JQuery 2.0 drops support for IE < 9

Show all headers | View raw

On 12-07-18 11:18 PM, Stefan Weiss wrote:

> Yeah, I read that too. It sounds more drastic than it actually is. From
> what I've read, they're creating a version 2 which is targeted at
> clients that don't require all the handholding and workarounds that
> earlier IE versions needed. It makes certain assumptions (for example,
> that methods like document.querySelectorAll are available natively),
> which means that a lot of code can be cut. This version can then be
> deployed in controlled environments or delivered to certain mobile
> devices. It's not meant to be used on the web without a fallback.
> Meanwhile, development for the 1.x branch continues in parallel with the
> 2.x branch.

And this is because the Zepto project cut into the project's
market on mobile devices. A self-fork is a disastrous move, and
leads one to question the competence of the developers behind
the project.

> I think it's a good idea. The collection of tools and methods that I use
> (and sometimes call a "library") has dropped support for quirks mode
> some years ago. It works because I know where it's deployed - in
> websites where I have control over the markup. Supporting quirks mode
> would serve no purpose at all, it would only add a lot of unnecessary
> code branches. Unfortunately, I don't have the luxury of being able to
> ignore older browsers just yet. As soon as the last of those clients is
> gone, I'll be removing code and dropping support, too.

It's a reflection of a poor design. An API that couples itself to
a certain subset of browsers will always be unstable. Optimally,
the developer should be able to choose what features to support
when implementing the API. This is the design I stick to, and I
know David Mark has implemented something similar.

There are certain cases such as Text Node traversal that need
a fork to function, but deeming such a fork optional nullifies
the potential damage it can cause in the future.

That fork alone underscores the importance of an optional API,
which is something that the jQuery project is beginning to
figure out, but will probably take months to years to implement
because of interspersed dependencies.

> The drawback is that the jQuery devs will have to support two different
> code bases, likely for a very long time, and that they will have to deal
> with the inevitable complaints by people who downloaded the newest
> version without bothering to read the instructions.

Their ignorance does not merit my pity, nor anyone else's.

-- 
Matt McDonald: Web/Flash Developer; Edmonton, Alberta, Canada

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

Thread

JQuery 2.0 drops support for IE < 9 perryv@gmail.com - 2012-07-18 20:43 -0700
  Re: JQuery 2.0 drops support for IE < 9 Stefan Weiss <krewecherl@gmail.com> - 2012-07-19 07:18 +0200
    Re: JQuery 2.0 drops support for IE < 9 John G Harris <john@nospam.demon.co.uk> - 2012-07-19 08:53 +0100
    Re: JQuery 2.0 drops support for IE < 9 Matt McDonald <matt@fortybelow.ca> - 2012-07-19 08:18 -0600
      Re: JQuery 2.0 drops support for IE < 9 Stefan Weiss <krewecherl@gmail.com> - 2012-07-19 23:20 +0200
        Thunderbird's posting behaviour (was Re: JQuery 2.0 drops support for IE < 9) Mike Winter <usenet@michael-winter.me.invalid> - 2012-07-19 22:37 +0100
        Re: JQuery 2.0 drops support for IE < 9 Hans-Georg Michna <hans-georgNoEmailPlease@michna.com> - 2012-07-20 15:11 +0200
  Re: JQuery 2.0 drops support for IE < 9 Gregor Kofler <usenet@gregorkofler.com> - 2012-07-19 12:46 +0200
    Re: JQuery 2.0 drops support for IE < 9 Gene Wirchenko <genew@ocis.net> - 2012-07-19 11:01 -0700

csiph-web