prototype.js tries to loose one "flaw"

[petermichaux]

Hi,

I didn't see this in the archives here and since prototype.js comes
under heavy fire now and then I thought some may be interested in what
they are planning next...


From
http://encytemedia.com/blog/articles/2006/05/23/prototype-inheritance-madness

"There was once a time where Prototype modified Object.prototype,
causing jaws to drop and eyes to bulge. Some were so turned off by the
decision...."

From http://sam.conio.net/, the creator of Prototype.js

"Justin suggests Dean Edwards' Base[1], which solves six problems[2]
with OO programming in JavaScript. I like Base because it's simple,
clear, and born from someone who's felt the pain of writing real
JavaScript applications.

"I don't have a roadmap for Prototype, but version 2.0-the next
major release after 1.5-will focus on polishing what we have now, not
on adding new functionality. You can expect Base to make its way into
Prototype 2.0 in a form that's backwards-compatible with Class.create
and Object.extend."

[1] http://dean.edwards.name/base/Base.js
[2] http://dean.edwards.name/weblog/2006/03/base/

 

[Richard Cornford]

I didn't see this in the archives here and since
prototype.js comes under heavy fire now and then
I thought some may be interested in what
they are planning next...

From

http://encytemedia.com/blog/articles/2006/05/23/prototype-inheritance-ma
dness
<snip>

It is often informative to go to a web page and then have it pop-up
"line 417 'object expected'" with sufficient frequency that it becomes
necessary to turn IE's error reporting off. Not only can the author of
the code on that page not cope with cross-browser scripting but they
cannot even cope with IE 6.

Richard.