I think it was MooFTW (though we are lacking love from mr Walsh here, hahaha).
I also still use MooTools probably daily, mainly Core with some small More stuff maybe and with Aaron's Behavior because it's the f#ckin' shit, seriously. On top of that I just create things I need myself, which I think is how most users do that have been using Moo since v1 and are comfortable writing stuff for Moo and what not. Oh yes, don't forget latest moofx, just throw it in and work with it. It differs I think when you have to work in a team and are sort of forced not to use Moo. Thankfully I don't have that problem.. Let's be realistic, in 4 years a website might be broken because of old MooTools, or it has Mootools running with plenty of redundant code, but that site will need a rebuild every 2 years if not sooner anyway and you might end up with another or no framework then, I dont' think it's a problem.. just go with the flow you know.. I like Ember too, it uses jQ, so I'm stuck.. So, yes, what was this about again? MooFTW! :) On Tuesday, August 13, 2013 9:16:54 AM UTC+2, Tim Wienk wrote: > > On 13 August 2013 01:07, Ralph Slooten <axl...@gmail.com <javascript:>> > wrote: > > > > 1) Although MooTools will not actively be developed any more in its > present > > form, it will continue to be available via the MooTools website (ie: > builds, > > docs etc)? > > > > 2) The MooTools core-dev team will still continue "supporting" existing > > versions (eg: bug-fixes relating from newer browsers, mailinglist > support), > > and you will be pushing out new releases when fixes are applied (I > realise > > it's possible for developers to fork and send pull requests)? > > > > Many thanks, > > Ralph > > > > I understand the concerns, luckily these are questions that I and > others have answered before in this thread. MooTools Core is in a > state where adding features just to add features is a not necessary. > It's a Core and it does its job as a Core. Some newer approaches to > similar problems are available in Prime, but that's a different point. > > I actually think it's rather simple: If we can't support Core, or > offer a compatible version based on Prime (the basis of the new > projects), to keep our current users out of trouble, why would anyone > take another chance, start using any of the new MooTools projects and > hope it doesn't happen again? > > The user-to-user support offered on mailinglists and IRC are not > something we can completely control, obviously, but seeing the kinds > of reactions we get in this thread, I'm not very concerned about that. > I do, however, encourage all of you to try and help others out in here > and IRC. Even if you don't end up being actual help to someone, the > worst thing that can happen is learning something new. :-) > > As for the website, I'm sure you guys have seen the new-website-emails > on this list before the summer vacation season, that will probably be > picked up after the summer vacations. I am currently not sure how > it'll exactly come out, though I do agree Core should be there. In the > worst case I'll make sure the old website is served on a subdomain, > but I think we can make something good out of it. > > As I mentioned earlier, and Garrick mentioned something similar in an > earlier email as well, Prime offers some new approaches to problems > Core solves as well, and it'd be nice to create a new compatible Core > based on Prime (and Elements and other friends) internally. That way > it'd be possible to offer two important things: 1. A compatible new > Core, so people can use their Core-based code with Prime and friends, > and 2. for those who want to try Prime and friends, a transitional > path to these (since it could expose the Prime-and-friends-APIs as > well, rather than only using it internally). This is, like Garrick put > it, "just a thought" at this stage. > > Lastly, in case it helps, MooTools Core is used in all projects that > use javascript at my company as well. > -- --- 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.
