You mean - my own mootools page? ;-)
On Sep 28, 10:55 am, Arian Stolwijk <[email protected]> wrote: > "Best way to make something happen is to do it" -- Arian, 2011 > > :P > > > > > > > > On Wed, Sep 28, 2011 at 10:25 AM, Robert <[email protected]> wrote: > > Developers has to convince designers / business people that mootools > > is the way to go. And for this the best way is to show its excellence > > and large user base. I know because I "pushed" mootools for some big > > projects in my company. And they always ask: why use mootools when > > even MS uses JQuery? Then I have to show them same fancy effects and > > say "it is easier/better then JQ". > > > Apache don't need to market itself because everybody knows it is best. > > Mootools doesn't have this position. > > And less developers means less code to reuse, less recognition, which > > means less developers, and so on. > > > Once Mootools has fame for its animations. Now we should pin some > > points where MooTools shines and market it with this in mind. Maybe we > > should work with Joomla people, they are probably the largest group of > > mootools users out there... > > > On Sep 28, 9:00 am, Barry van Oudtshoorn <[email protected]> > > wrote: > > > On 28/09/11 14:33, Robert wrote:> But webservers are for geeks and js > > frameworks are (in many cases) > > > > also for designers. > > > > Hmm, I think that in the case of MooTools, the former is far and away > > > the larger target demographic. Yes, you can achieve fancy effects in > > > MooTools; you can do just about anything in MooTools that you can in > > > jQuery. The difference, and what I believe the website should promote, > > > is that MooTools is about writing code. > > > > I think that generally speaking, people perceive the toolkits something > > > along these lines: > > > > jQuery: quick, easy, fancy; it lets you manipulate the DOM and layer > > > effects onto existing documents. > > > YUI, Dojo: big frameworks for developing apps; the "enterprise" solution > > > (ugh). > > > MooTools: All and none of the above. > > > > (Yes, there are more frameworks. No, I'm not going to list them. :P) > > > > MooTools is not, to my mind, a framework to facilitate DOM manipulations > > > (although it does do that). Neither is it a UI toolkit (although you can > > > build/find one using it). MooTools is to JavaScript what a blowtorch is > > > to a crème brulée: the tool that makes it exceptional, rather than just > > > great. > > > > I think that MooTools should be targeted primarily at developers, but > > > with a note to the effect that "Yes, it does X/Y/Z, too -- and well!" > > > Looking at the people who post to this mailing list, they're generally > > > developing fairly large-scale sites/apps using MooTools. In my opinion, > > > these people should be the target. > > > > - Barry > > > > -- > > > Barry van Oudtshoornwww.barryvan.com.au > > > > Not sent from my Apple πPhone.
