> The decline of MooTools rests on the MooTools core devs and no one > else.
Yep, it is/was principally an internal problem (including the community as well) but I think you're whitewashing if you think Microsoft didn't buttress jQuery *in part* because jQ couldn't possibly compete design-wise with their OO product lines. Every .NET dev I know accepts that jQuery must be "good enough" if Microsoft chose it. Yet jQuery is "bad enough" that it keeps them from being compelled by native JavaScript and JS developer-focused frameworks; it keeps them thinking JS is basically what the world thought it was in 1995. And that belief keeps them away from building single-page clients against Node.JS, for example. Think about Microsoft actively embracing PHP over Python. And I'm a huge PHP guy, but I don't think that was _solely_ because PHP is the dominant language of the web; it also protects their products, because PHP will rarely be compelling to an experienced .NET dev (except maybe for selected tiny projects). Trust me, it's not "Microsoft's fault" that Moo is where it is, but nothing happens in a vacuum. jQuery is BY FAR the crappiest Big Thing in circulation right now, and just so happens to be embraced by the once-leaders in ensuring that crappy Big Things spread far and wide. Like the conspiracy freaks like to retort, "So you're a coincidence theorist?" :] -- Sandy -- --- 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.