No, that is far from clean, much less cleaner than prototype. You mean init as in like, a consistently named constructor across classes? So if I look at class y, and class x I can easily see which method is the constructor for the class, and you mean to say that's, like, unclean? Are you serious?

Just say "I prefer procedural programming over object oriented, and thus like other libs over proto because I don't need clean consistent class based object oriented js code" and stop thrashing the core lib represented and adored and used and generally supported by the people in this list.

Don't make me come over there! I'll jump into the YUI list or forum and start picking it apart.

:-)

On 7/19/06, Peter Michaux < [EMAIL PROTECTED]> wrote:
On 7/19/06, Ryan Gahl < [EMAIL PROTECTED]> wrote:
> Protoype is important if only for the ease with which it enables class based
> OO programming in js. Yes, we all know... js is a prototyped based OO
> language, but using a traditional class approach makes code re-use,
> readability, and refactoring (read maintenance) so much easier. I'm guessing
> the OP with the beef against proto is more into procedural style programming
> (which is FINE, please don't everyone jump down my throat about that
> comment... :-)


There are a lot cleaner ways to do OOP in _javascript_ without all that
init function business

http://www.kevlindev.com/tutorials/_javascript_/inheritance/index.htm

Peter
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to