Another way to look at this is that as an open source project, MooTools wasn't that good. MooTools has *excellent* code. Still better than a lot of frameworks out there. But the people who wrote most of it focused on that rather than the *process *of writing that code. The process of recruiting new developers and democratizing the power to change the project. So when all the main developers got hired away to places that didn't pay them to continue developing the project (Facebook, Twitter, Spotify, and many others) and/or they had families and less time to work on things etc. Because we didn't spend our time giving the keys to the project to others, there's no one left actively working on the project.
As Nathan points out, the world moved on. MooTools itself isn't that interesting anymore; one could argue that it solved the problem it set out to solve and works great. I still use it and there's nothing wrong with it. I still actively push to my behavior (github.com/anutron/behavior) and MooTools Bootstrap (github.com/anutron/mootools-bootstrap) branches all the time. But is it interesting work? Not especially. The need that MooTools filled in 2006 just doesn't exist anymore. There's a giant ecosystem of solutions for various needs out there. There's no reason to focus on monolithic solutions. So both these things are true. MooTools itself is lacking new blood to fill in where the old has moved on, and the world changed such that putting a bunch of effort into MooTools itself just doesn't make a lot of sense. -a On Sat, Aug 10, 2013 at 4:26 PM, Nathan White <changereal...@gmail.com>wrote: > Mootools made the Internet a better place. Providing sane shims for > browsers and a super elegant API. It improved upon many things and > ultimately frameworks like jquery are better as a result of Mootools. > > It's not so much about Mootools is dead or people don't care. Things have > evolved rapidity. One of the biggest paradigm shifts is extending the > native prototype. The world at large has considered this evil. This leaves > Mootools in a precarious position and no you cant just change it without > changing the interface. things like selector engines that were really > important a few years ago just don't matter anymore. The trend is micro > frameworks. There isn't anything that stops you from using the patterns or > Apis in your own code. > > The beauty is we have gained so much more. We can use libraries like > modernizer without having to implement the cruft into frameworks. > > Code becomes cleaner... Smaller. > > Right now I'm in the process of porting old Mootools code to something > new. The way I'm achieving this is by using the component.io builder. > There is a lot of code already in that ecosystem that won't make a Mootools > developer shiver. Lots of it is lower level like component/dom. But there > are some magical things like model and reactive for elegant two way data > binding. So much richness. Npm packages like "async", "moment", "is" are > all aready componentfied for the browser. It's super easy to fork, deploy > and manage in your own production environment. > > The thing is everything is moving so fast, Mootools isn't. Take the code, > inspiration and ideas and pass them on to the next gen of dev. > > Stand on the shoulder of giants. > > > > On Aug 10, 2013, at 6:55 PM, utan <vcomputado...@gmail.com> wrote: > > @Tim Wienk, > > I know still supported but splitting a project to start something new is > not a good idea and always end up leaving the previous one alone to die, > If it were to say that they are making kind of plugins to be used with > Mootools core then I would say they will keep alive.. or that Prime will > use of > Mootools Core well that will be good but not they aren't doing that. > > What's the matter with mootools as it is? it's just because doesn't have > the bunch of supporters Jquery has? as it stand Mootools is rock solid why > start > some other project when this is so good to keep and to improve.. > If it were because they extended the prototype the reason to leave the > code alone is a bad idea, why not just stopping extending the prototype in > latter > versions of Mootools, > what's the matter with mootools as it is? > > This is me , just trowing my frustrations.. nothing against anyone. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "MooTools Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mootools-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "MooTools Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mootools-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "MooTools Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mootools-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
