Web Predictions For 2009

By  on  

A new year usually brings hope of better things. It also bring expectations and wonder. Here are my (unfounded) web predictions for 2009.

1. A JavaScript Framework Will Fall

I believe that a JavaScript framework will fall in 2009. I really wouldn't be shocked to see one go. I don't want to share which I think will fall, but the popularity of jQuery, coupled with the lack of progress being made on a few of them, makes me feel as though at least one will die off.

2. Firefox's Usage Will Grow Tremendously...

I believe more businesses will steer their employees toward using Mozilla Firefox and thus increase Firefox's usage. Internet Explorer's sluggish performance coupled with Firefox's feature set will make IE a secondary browser for many businesses.

3. ...But IE Will Continue Its Reign

Too many users simply take what they're given and this will not change. Internet Explorer 6 and 7, and on a lower usage level 8, will continue to dominate the browser market share.

4. MooTools' Popularity Will Grow

MooTools will release a plugin forge which will quickly become a treasure chest that will attract many web developers.

5. Developers Find Out: Knowing One Framework Isn't Good Enough

While being an expert with on JavaScript framework is great, developers will realize that knowing one framework isn't good enough. Porting plugins from a different framework to the developer's preferred framework will become tiresome and the process of reinventing the wheel will be the motivation pick up another framework.

Have any predictions of your own? Am I crazy? Share!

Recent Features

Incredible Demos

  • By
    Form Element AJAX Spinner Attachment Using MooTools

    Many times you'll see a form dynamically change available values based on the value of a form field. For example, a "State" field will change based on which Country a user selects. What annoys me about these forms is that they'll often do an...

  • By
    HTML5’s window.postMessage API

    One of the little known HTML5 APIs is the window.postMessage API.  window.postMessage allows for sending data messages between two windows/frames across domains.  Essentially window.postMessage acts as cross-domain AJAX without the server shims. Let's take a look at how window.postMessage works and how you...

Discussion

  1. David,

    Did you make a prediction last year that MooTools would implode or fork? I know someone did, but I can’t remember whom.

    Did MooTools fork recently?

    Justin Noel

  2. cssProdigy

    David, Your not crazy.
    I hope Firefox usage grows, in 2009 I just might be able to fully drop IE6 and forget about it. The MooTools plugin repository will be nice. I love what the JavaScript frameworks are doing and seeing anyone of them fall isn’t pleasant. With what MooTools is doing it’ll definitely grow.

  3. It seems like everyone in the web niche blogs has IE6’s downfall on their hopeful resolution/new years wish list. It’s too bad that the people still using IE as a primary browser will probably never see it. Here’s hoping for next year!

  4. @AppBeacon: I’d never say that Moo was going under! ;)

  5. Keith Wolf

    Despite my hopes and dreams for an IE6-less world, my main project will continue to require me to test primarily in 5.5 & 6… internal corporate networks, at least my company’s, just don’t seem to learn.

    Hope you had a good new year, and I am glad to have found your blog.

  6. @Keith Wolf – Wow! 5.5 still? That really sucks.

  7. You want predictions? Now THESE are predictions:
    http://agitationist.com/2009-predictions-for-the-interweb
    Inspired partially by your post (link love in line one!)…

  8. LockWesMonster

    I don’t see why Microsoft couldn’t release browser updates that fix PNG/other css issues for IE6 and IE7 when they recently had the critical update for all of their browsers. It seemed like a convenient time to roll something out. I really wish that anyone who installed the Zero Day Attack update would have been automatically updated to IE7.

    But that would be too simple, wouldn’t it?

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