Dimitar - I'm not disagreeing that MooTools is not an easy framework to jump, but it iterates an earlier statement I've made (many times) MooTools is for JavaScript developers. It's not meant for any random person to jump in and say "hey! I like what you did there, I want to do it" - jQuery is built on that kind of ideology (in my opinion) and as such their community is full of eager people who like to help out other people because they're all kind of "learning together" or whatever analogy you care to use (not 100% accurate, but I digress).
MooTools is more for those that get JavaScript in general, or are furthering their knowledge. It's not a "beginners" community or framework in my opinion, and I was lucky to work with a couple great MooTools developers who helped me learn my way into it, which most independent users don't get. -kb On Nov 1, 1:42 pm, Dimitar Christoff <christ...@gmail.com> wrote: > > I took it to mean - MooTools (and really, the community in general) > > encourages you to adhere to the "better" practices in your coding, > > period. It's not facetious > > I would disagree - it is kind of funny because it works in an odd way. The > problem is, the so called community (the core / more team + usual > suspects on the list and twitter) are quite subjective in one regard - > it all looks very easy from the top but paving the way for new comers > and relative new comers can be considered beyond what's called for. And > yes, resources are available but it's a different matter if they "read" > well to those that don't know what a dollar sign is yet or try to figure > why our $ is not the same as jQuery's... > > Once you "get/grock mootools" you are able to extract far more > meaningful help and advice and can appreciate and understand what the > others do. So these practices we speak of, you start to spot them, then > to question them and look them up. But often, there is no real > explanation available in the code/comments or on the list. > > For example, understanding namespacing but also understanding the impact > on overall performance, on noconflict mode and the extent to which a > mootools based prototypical script can play nice - it's a bit much to > get right from the source code of a snippet by davidwalsh.name :D > > I guess all I am saying is, not everything is obvious to those that > start from the ground up. What and how you code as a part of your > subconscious (or nott) routine often will not come easy to others... So > why not put a guide of sorts of the latest and best trends in js / > mootools / performance and how they can be applied to our code? > > This is the one thing we lack over jquery - better support and a broader > entry funnel imo, but there should be resources / guidelines for the > top-end too... > > Kind regards, > -- > Dimitar Christoff <christ...@gmail.com> -http://fragged.org/
