I'm in a similar situation to Aaron -- I still use MooTools extensively:
it's at the core of all of the products I develop. Like Aaron, when I
need something, I build it: this helps with internal consistency and
also makes sure that whatever I build does exactly what I need it to do
-- no more and no less.
From my perspective, MooTools as it currently stands is in a really
good position (from a code standpoint): there aren't any major issues or
problems. As I go forward and drop support for legacy browsers (fingers
crossed for no more IE8 from 2014), I'll probably start removing a lot
of the now-redundant code from MooTools: for example, I won't need an
implementation of `bind`, so why push that code across the wire? If I do
that, I'll do my best to make sure I do it in a fork.
To my mind, the beauty of MooTools is that it allows you to write JS
that Just Works, with a couple of nice extras thrown in (like Class).
Ultimately, though, as ES evolves, only those extras will be left --
which is, perhaps, where things need to move anyway. MooTools occupies a
very specific niche: I see it as a low-level application development
framework. That is, it doesn't force you into a certain pattern/toolset
like, say, YUI or Dojo do, and it makes application development much
easier than, say, jQuery.
On 13/08/13 05:05, Aaron Newton wrote:
FWIW, I'm building things on MooTools today. We don't have some of the
needs that might force me off it (a thick client with server push for
example). When I look at the landscape, there's still no better
framework for doing this kind of work, IMHO. I just don't rely on the
community that much; that is to say, when I need something, I write
it. I'm still very much enamored with my Behavior stuff (so much so
that I've been contemplating porting it to be framework agnostic). You
don't have to stop using MooTools. Just don't expect it to solve all
your problems (thin client stuff, and while it works fine for mobile,
it's payload - e.g. file size - can quickly get out of hand).
I'll reiterate to the community here: the best way to make MooTools
last is to start working on it directly. Don't get frustrated if you
don't have commit rights; there's a reason it's so easy to fork things
on Github. If you started working on a version of MooTools that added
a few features and fixed a bunch of bugs, the next thing you know
you'll probably have people sending you pull requests on your
unofficial version. When that happens, the core-dev team will start
asking if you want commit rights. YOU can make things happen. You just
have to do it.
On Mon, Aug 12, 2013 at 1:06 PM, utan <vcomputado...@gmail.com
<mailto:vcomputado...@gmail.com>> wrote:
Yeah,
As I thought you are saving memory using the prototype but it
looks verbose to me, somehow I knew Mootools was using the
prototype internally but the outside would be as creating a raw
object without prototyping, Now Arian's classy needs Prime as
requirement right or not?
Can I use it on the browser alone or its just node.js only..
I like Mootools class so I want to stick with something similar
which will give me performance, for me saving memory its
performance wise.
--
---
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
<mailto:mootools-users%2bunsubscr...@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.
--
Barry van Oudtshoorn
www.barryvan.com.au
--
---
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.
