We're planning to shift to native JSON support in our 1.7 release.
Unfortunately, our implementation of JSON was based on Doug's initial
one, which used different semantics altogether.
It turns out that the steps we took back then to avoid naming
collisions (using the toJSON method named rather than toJSONString
which Doug's initial implementation used) have turned against us. So
defaulting to the native implementation might cause some small
backward-compatibility issues for some of our users, hence the wait
for a more important release.
Your patch is of course more than welcomed!
I'm not sure what you mean by event wrappers in Webkit (nor in other
browsers). Currently, we extend Event.prototype in standard-
compliant browsers with a couple of methods. And extend event
instances in IE before passing them to listeners. In neither cases are
the elements wrapped. In webkit, the cost is negligible, as done once
at runtime on Event.prototype.
I heard from Sam that you had made significant performance
improvements to the Array iterators. If you have a patch there too,
that's again welcomed.
On Mar 10, 4:05 pm, Rob Tsuk <robt...@gmail.com> wrote:
> On Tue, Mar 10, 2009 at 8:02 AM, Ryan Gahl <ryan.g...@gmail.com> wrote:
> > Hi Rob... AFAIK, in the "bleeding edge" SVN versions of Prototype, they are
> > making use of the native JSON parsers if present. I could be wrong, but I
> > believe I saw that somewhere. I'll leave it to one of the core dudes to
> > comment further though...
> Oh, good point, I'll go look at the latest sources. I haven't done that in a
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to
For more options, visit this group at