@Oskar
Ditto on a moo-centric bias. Asking the following (especially via the
community) is difficult.
"the day where all Moo has to be rewritten into something else is getting
closer and closer. Actually I've started pushing a rewrite forward"
I think many of us would like to know what your strategy is with this,
especially around existing applications built on mootools, i.e., what are
you switching to, how are you going about it, and how much of a struggle
has it been thus far? For context, how big are the respective code base(s),
who is the user/audience, etc.? Do you have any examples?
Learning a new framework is the easy part... migrating thousands of
features with dozens of plugins to something new seems Herculean.
Johnny Fuery
President/Principal Engineer
Fuery Solutions -- makers of MerusCase
1736 Franklin Street, Suite 350
Oakland, CA 94612
510.550.5000 Main
925.997.3878 Mobile
510-836-0915 Fax
j...@fuery.com
On Mon, Aug 12, 2013 at 1:08 PM, Oskar Krawczyk <oskar.krawc...@gmail.com>wrote:
> Rich, here's my take on this, I might be brutally honest, *I still love
> all <3 Moo core-devs*.
>
> DISCLAIMER: I've been a die-hard Moo user. *Every project I've made for
> the past ~8 years was using MooTools*. I've build JSFiddle.net and
> Positionly.com using Moo. I've actually learned JS with Moo.
>
> For the past few years I've came to a conclusion that using MooTools
> everywhere was just plain ignorance on my side, I refused to acknowledge
> other frameworks because in my eyes Moo was always the best.
>
> At this point it's insanely difficult to find a front-end developer who's
> willing to work with MooTools - I've been looking for a in-house developer
> for nearly a year now. Community around MooTools is pretty much
> non-existent in comparison to other communities. Moo Plugins/libraries are
> long-forgotten and not maintained anymore (there are just a few that are
> regularly contributed to, mostly by the author not by others). This
> situation is getting pretty frustrating as I mostly need to write my own
> custom things, instead simply use an external lib - I have no time for
> this, guess why, because I can't find anyone to help me...
>
> As I've mentioned before, the day where all Moo has to be rewritten into
> something else is getting closer and closer. Actually I've started pushing
> a rewrite forward.
>
> If you really want to learn something new, pick up CoffeeScript and some
> small non-intrusive, highly-maintained library.
>
> Peace,
> Oskar
>
> On Aug 12, 2013, at 12:47 PM, Rich Lloyd <richtu...@googlemail.com> wrote:
>
> I've been using MooTools for the last few years now, love it, I've only
> just discovered and signed up to this group to read that MooTools will be
> no more.
>
> As an experienced developer, MooTools is perfect for the fluid interactive
> user interfaces I produce. Hate it that so many developers see the UI as a
> skin to the back end and resort to jQuery, I also hate seeing more and more
> of new era 'front end' developers (they all seem to use jQuery as if it's
> cool) who copy and past code to get things to work, it doesn't work, so
> they constantly ask for help, yet still charge a full day rate. (Sorry mini
> rant)
>
> My question is, what do we do? People are saying the MooTools core will
> remain supported, but will it? What are the alternatives? I have just
> started a massive project and I'm at a fork in the road, do I stick with
> MooTools (which I've already started the project in), or do I start using a
> new more modern technology that will be supported in years to come?
>
> Been coding for over 20 years, I'm happy to pick up new technology and run
> with it, that's not a problem, but I want to know what's new that MooTools
> can't offer?
>
> Should this be a new post?
>
>
> On Saturday, 10 August 2013 04:19:09 UTC+1, utan wrote:
>>
>> Can't get my head to learn the Jquery way.
>> Mootools' way.
>>
>> var foodiv = $('foodiv');
>>
>> var div = new Element('div' , {
>> id : 'someid'
>> }).inject(foodiv);
>>
>>
>> to Jquery's
>>
>>
>>
>> jQuery('<div/>', {
>> id: 'foo'}).appendTo('#mySelector');
>>
>>
>> Why mootools had to die?.. I am so disappointed ..
>>
>> sorry just frustrated trying to learn something that goes against what I
>> have learned the right way.
>>
>>
> --
>
> ---
> 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.
>
>
>
>
> --
>
> ---
> 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.
>
--
---
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.
