Re: Why should I eschew prototype.js?

nolo contendere meinte:

Again, this may be the browser's fault then. Bear in mind that browser
developers do have to cater to existing web pages, and have all sorts
of testing to try to ensure that nothing breaks in future versions.

You know what? There are websites (not conforming to standards, sure), wich looked perfectly ok on IE6, but break more or less seriously on IE7.

I highly doubt that just because a page doesn't conform to ECMA
standards, the browser developers will say "screw that web page, if
they don't follow ECMA they don't get a proper rendering in our
browser." This may work if the percentage of "bad" web pages were
vanishingly small, but hey, this is the real world where people are
stupid and market share is of vital importance to a browser's
continued existence. I'm not saying I'm encouraging bad coding, or
stupidity, but I'm being a realist. Once all market share is captured,
THEN you can begin to gradually enforce whichever standards are the
best. But until then, it's a free-for-all.

Websites all break in different ways. It's impossible to care about all of them.

I truly do appreciate your perspective. I did a little research on
you, and you appear to be a very intelligent individual, although (and
I don't mean to be destructively critical) a bit of an idealist/
purist--which the world does need, but isn't the way the world works.

What's your point? You're looking for points against prototype, but whenever points follow you dismiss them with empty statements.


Again, if they are so trivial, why wouldn't a "good" library have been
written?

Perhaps mine *could* be better. But I don't want to put in all the effort needed for proper testing and documentation. And I deem those things important, when publicising a library (contrary to the prototype authors). Other authors might have similar or other reasons.

Wouldn't evolution cause the "good" librarues to bubble up
and become the de facto standard? Wouldn't "bad libraries" break in
future revs, independent browsers, etc, and the "good libraries" gain
mind- and market-share with each manifestation of the "bad
libararies'" failure?

I suppose that's the reason, why the least standards compliant browser has the marginal market share of, say, 80 percent?


Gregor


--
http://www.gregorkofler.at ::: Landschafts- und Reisefotografie
http://www.licht-blick.at ::: Forum für Multivisionsvorträge
http://www.image2d.com ::: Bildagentur für den alpinen Raum
.

Relevant Pages

  • Re: Development with IE 7 for non-Windows users.
    ... still displaying it using the developers chosen method as a default. ... and standards compliant, but the reality is that the Internet is a segmented ... market with a menangery of browser platforms in use by users. ... sort of compromise in applying the w3c styling standards and at the same ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Development with IE 7 for non-Windows users.
    ... and standards compliant, but the reality is that the Internet is a segmented ... market with a menangery of browser platforms in use by users. ... I don't want to bash Microsoft, but I feel this is starting to ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Firewall of SP2 is good?
    ... It's always easier to create your own standards than ... It's the marriage of the browser ... members, developers, and people in Redmond that were part of the core ... >> different than any other platform before it. ...
    (comp.security.firewalls)
  • Re: Development with IE 7 for non-Windows users.
    ... and standards compliant, but the reality is that the Internet is a segmented market with a menangery of browser platforms in use by users. ... Its impracticle to impose laws that require users only to use a browser that is fully compliant to w3 standards. ... It just makes sence to devote our development effort in proportion to the market exposure and usage of our target platforms/browsers. ... I don't want to bash Microsoft, but I feel this is starting to ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: AKICIF: Has anyone ever burned Fahrenheit 451?
    ... current web standards. ... They fail on some pages now; they'll fail on an increasing number of pages ... So you can live with the fact that your browser will keep breaking, ... For market share purposes, people should also try to ensure that their ...
    (rec.arts.sf.fandom)