When JavaScript Frameworks Collide

By  on  

Though their theories on JavaScript coding differ, JavaScript framework developers keep a tight lip when it comes to commenting on other frameworks. When another framework is brought up, the developer usually gives generic responses like "they're doing good work" or "they've got a unique approach." Anything outside of this response seems to gain unwanted attention, which is exactly what MooTools' Olmo did last week.

Here's the sequence of events that led to his eventual departure from MooTools:

  1. Olmo gave a presentation about MooTools in which he said some inflamatory comments about the jQuery framework and posted it on the official MooTools Blog. The blog post has been taken down but you can view the video below.
  2. jQuery developer John Resig wrote an article entitled I Learned Some Things About jQuery Today. The article was a sarcastic piece summarizing the offensive points of Olmo's presentation; it got quite a bit of attention.
  3. MooTools lead developer, Valerio, expelled Olmo from the project and wrote a very sincere apology on the MooTools blog. Read the comments -- they're quite interesting. Some parting shots were taken by Olmo toward another MooTools developer Aaron Newton.
  4. Olmo replied directly to John, apologizing for his comments.

Though Olmo's comments were interesting, they were also unfounded and irresponsible (from the mouths of John, Valerio, and Olmo himself). Check out he video for yourself.

Olmo's Presentation


LA Developers Meetup - OCT 7 - Olmo Maldonado from will jessup on Vimeo.

Prototype vs. MooTools vs. jQuery

Prototype team member Justin Palmer wrote an article about articles that compare the major JavaScript frameworks. This stirred up fury from the jQuery camp. MooTools developer Aaron Newton chimed in and unintentionally threw more fuel into the fire. Check out the article.

Recent Features

  • By
    5 Ways that CSS and JavaScript Interact That You May Not Know About

    CSS and JavaScript:  the lines seemingly get blurred by each browser release.  They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely.  We have our .js files and our .css, but...

  • By
    Introducing MooTools Templated

    One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating: new Element Madness The first way to create UI-driven...

Incredible Demos

  • By
    Create a Sexy Persistent Header with Opacity Using MooTools or jQuery

    I've been working with the Magento eCommerce solution a lot lately and I've taken a liking to a technique they use with the top bar within their administrative control panel. When the user scrolls below a specified threshold, the top bar becomes attached to the...

  • By
    WebKit-Specific Style:  -webkit-appearance

    I was recently scoping out the horrid source code of the Google homepage when I noticed the "Google Search" and "I'm Feeling Lucky" buttons had a style definition I hadn't seen before:  -webkit-appearance.  The value assigned to the style was "push-button."  They are buttons so that...

Discussion

    Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!