I started working with MooTools early this year and chose it because it looked like I could write cleaner, more maintainable code via classes instead of JQuery.
I have to admit that when first compared them, JQuery without a doubt looked much easier to learn. Their website and examples perfectly show you how to get up and running right away. Nevertheless, I chose to learn MooTools because of its classes. So far, I am very happy with what I have done with MooTools and my classes are very clean, reliable and well organized. A few things that run through my mind are: 1) can you write clean code with JQ? I am far from being a JavaScript expert and I've written some horrific JS code. Moo allows me to write very clean and maintainable code. 2) I am guessing that the number of free widgets and community support is far better by going JQ but what other benefits do you get with JQ? 3) I am assuming that future browser issues will not cause me problems by developing with Moo. What are your thoughts on this? At this moment, #3 is the only concern that I have. I plan to make a mobile version of my app (hope that this will not be a problem using Moo). On Tuesday, August 20, 2013 9:57:58 AM UTC-5, stratboy wrote: > > http://www.flibbr.com/blog?id=1 > > Il giorno domenica 18 agosto 2013 22:40:33 UTC+2, dukeofgaming ha scritto: >> >> I have been a MooTools fan ever since I knew the framework, however, I >> now understand that the new direction is prime. >> >> I understand that there have been lessons learnt, and practices like >> extending native prototypes had to be abandoned. >> >> I understand that the new direction is to adopt the microframeworks >> apprach and new best practices and libraries that involve >> package/dependency management and server side javascript with Node. >> >> What I don't understand is why none of this exciting direction has been >> communicated to the evaporating user base. I think MooTools still has a >> nice community, and I bet part of it is dormant. >> >> Why not fill-in the community with a simple blog post in the MooTools >> blog?, why not make a simple website for prime?, why not publish some >> examples with prime? >> >> I don't feel confident anymore about using MooTools because I feel that >> my code will be already dead. I don't feel confident about using prime >> because I don't know what it's direction will be, is it an academic >> experiment?, is it already being used in production environments?, is it >> being used at all?, is it a serious project or just toy code? >> >> If people started using prime it would evolve quicker, but right now all >> that is happening from my point of view is that the MooTools community is >> slowly being alienated away. >> >> So why not let us know what your plans and vision with prime are?, I >> think a simple blog post and a very simple website would do to reinvigorate >> the community. >> > -- --- 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.
