On 12/3/06, tobie <[EMAIL PROTECTED]> wrote:
>
>
> Peter,
>
> What is it exactly that you are trying to do? Drive Prototype users
> away from Prototype to your own library?


He has the right to criticize the framework. His points are valid, although
he sounds like the library is completely hopeless - that's the part I don't
like.


With Prototype the added sugar has to be transmitted to the client. Also
> there could be an exotic browser bug related to the sugar code that is not
> detected during testing.


Since when do we fear browser bugs? We will work around them


About namespacing, see my most recent thread. I'd like you to leave a
comment on it...

A experienced JavaScript developer coming to a project using Prototype for
> the first time will be confused by the iterators when for loops could have
> been used.


That was me. I didn't understand Enumerable until Justin blogged about it. I
found it strange at first - now I love it. You have to be open minded.

About the bottlenecks, we'll try to work on it. For large arrays and huge
number of loops I revert to using for loops, but that's very rare.

YUI has the best JavaScript inheritance mechanism I have encountered
> that gives the closest Ruby-like behavior possible. It is simple and
> reinforces the ideas of prototype based inheritance when a developer
> is using it.


I don't see why Prototype doesn't. It just has sugar added to it -
Class.create(), Object.extend()


That's why I've gone my own way and started a new library for use with Rails
> that can just as easily be used outside of Rails and when I'm working with
> legacy code.


I've been reading your blog since before Fork. Your level of JavaScript
knowledge is admirable. Perhaps with all that ideas how to make a better
framework you can certainly come up with occasional patches/suggestions for
the Prototype framework on the ticket system, too? It's far from hopeless,
believe me ;)

--
Mislav


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to