From closures to prototypes, part 2

Prototype Vs Closure - optimisation d'une classe en JavaScript

Atteint de Javascriptite aiguë [Cyril DURAND] — Tue, 16 Oct 2007 12:48:01 GMT

En JavaScript, il y a 2 grandes façons de faire une classe : le mode prototype et le mode closure . Méthode

ASP.NET AJAX Beta 1 and ComponentArt Web.UI

Miljan Braticevic — Tue, 31 Oct 2006 20:52:06 GMT

We have recently completed converting our suite of user interface controls from the latest Community

Microsoft ASP.NET Extensions (Atlas) Beta 1 et ControlToolkit nouvelle version

Fox Blogs — Fri, 20 Oct 2006 23:29:48 GMT

Pour compléter le billet de Patrice il y a la beta 1 de Microsoft ASP.NET Ajax Extentions de dispo mais

Bye Bye Atlas et ses CTP, Bienvenue à la Beta 1 de Microsoft Ajax !

ASP.NET Français Blogs — Fri, 20 Oct 2006 16:30:52 GMT

Scott Guthrie l'annonce sur son blog via un billet fort détaillé. La version Beta 1 de Microsoft ASP.NET

re: From closures to prototypes, part 2

Bertrand Le Roy — Tue, 17 Oct 2006 22:14:17 GMT

Michael, Jon: it's imminent.

re: From closures to prototypes, part 2

Jon Flanders — Tue, 17 Oct 2006 22:04:23 GMT

Bertrand - any ideas when a public CTP using prototypes will be available?

re: From closures to prototypes, part 2

Michael Stuart — Tue, 17 Oct 2006 18:23:46 GMT

I had heard that the next release would be sometime this week. Do you know if there's any truth to that prediction? Thanks for these Atlas posts...they're very helpful.

re: From closures to prototypes, part 2

Bertrand Le Roy — Tue, 17 Oct 2006 01:03:50 GMT

Rick: this in principle doesn't change anything to type descriptors, which still need additional type information. The design for type descriptors *did* change, but for different reasons. More on that later.

re: From closures to prototypes, part 2

Rick Strahl — Tue, 17 Oct 2006 00:54:15 GMT

Bertrand, does this mean the syntax conventions will make it possible to forgo the type descriptor interface that's required in the current builds?

re: From closures to prototypes, part 2

Bertrand Le Roy — Tue, 17 Oct 2006 00:04:34 GMT

Ryan: from the *outside*, you need a way to tell public and private members apart. Users of your classes (and Visual Studio) must be able to determine easily if Foo.bar() or Foo._bar() is public or private.

Alex: from our benchmarks, creating an instance is between 3.5 and 16 times faster depending on the browser. Firefox is getting the biggest benefits. Calling members is a little slower on all browsers (between 8 and 58 percent) because of the need to lookup on the instance, then the prototype. But the biggest benefit is in terms of working set with the prototype model taking about 30 times less memory than closures. Finally, parsing times are about twice as fast on IE with closures, and four times as fast with prototypes on Firefox.

So all in all, closures are generally a little faster on IE, but prototypes really shine on Firefox. All this was with IE6 but I don't think the JavaScript engine was changed in IE7.

Of course, all those are micro-benchmarks so your mileage may vary, depending on your type of application.