DOMAssistant lives – version 2.6 released with overall fastest CSS selector performance and plugins

Almost a month ago, I wrote a hesitant post about DOMAssistant in DOMAssistant – Why bother?, so it’s about time to talk about that again.

At the time, I was feeling generally low and a bit insecure about what I wanted to achieve, and what my priorities were. The response to that post was overwhelming, both in the comments and the people who contacted me through e-mail and instant messaging.

Thinking about how it mattered to a lot of people, it also helped me realize that I like what I have achieved with it. I analyzed DOMAssistant and compared it to other JavaScript libraries, and also felt that I really had something to offer. Factors like being lightweight, having very good performance and being flexible inspired me to continue developing DOMAssistant, and make it even better.

The last month, I’ve put a lot of work into it, hence the sparse blogging and mangy parrot state. But the result, I think, is very very good!

And don’t worry, I wouldn’t code something in my free time unless I was completely motivated to do so. Coding things you don’t want to, but have to, is referred to as “work”, and is a completely different story. :-)

Releasing DOMAssistant 2.6

I’ve just released DOMAssitant 2.6, and lots of things have changed, and the code is mostly refactored:

There are a number of improvements and new goodies in the new 2.6 version, so please check out the release blog post in the DOMAssistant blog.

Credits

I would also like to express my gratitude and thanks to the DOMAssistant Team for helping me out and pushing me to make it even better. I’d like to also direct another thank you to Niklas Lindström for being there for me in the darkest hour of performance issues and mental despair.

Posted in Developing,DOMAssistant,JavaScript,Technology |

17 Comments

  • Great work, Robert! I think you can be very proud of what you’ve accomplished (especially when viewing the Performance test).
    The plugin-system also looks very nice.

    Overall: kudos! Keep it up :)

    By the way, who’s in your DOMAssistant team and do you have the need for more people?

  • Andreas says:

    Absolutely brilliant work. I may have to abandon jQuery.

  • chenghong says:

    Congrats Robert, for getting 2.6 out of the door as well as the blazing selectors speed.

    WebKit took like.. 20ms to finish the test? My jaw dropped to the floor..

  • Pelle says:

    Congratulations Robert! This release is really exciting!

  • Johan Borestad says:

    Excellent work Robert! Very impressive :) I'll have to try this really soon.

  • Another impressive release. I might have to try and ween myself from my LowPro addiction, and take DOMAssistant for a real spin on a real project soon.

    The speed tests certainly makes a very compelling case for DOMAssistant, with a lot less bagage than competing frameworks offer.

    When evaluating tools for new projects, DOMAssistant should certainly be taken for a spin round the block, with some kicking on the tyres.

    Congratulations Robert!

  • Congratulations Robert, excellent work.

    I do think DOMAssistant definitely has a place in the somewhat over crowed JavsScript library market.

  • Diego Perini says:

    Awesome work Robert,

    I like your coding style and the speed tests you showed are incredibly fast.

    Don't let the low parts of life bring down your project, it has a bright future.

    Your framework surely deserves a place between developer choices.

    Diego Perini

  • Patrick says:

    Holy moly! I am totally stunned at how fast it is…

    Have to take a closer look at DOMAssistant.

    Thanks and keep up the good work.

  • Robert Nyman says:

    Thanks everyone, really! I'm quite happy with this release, and definitely feel that DOMAssistant has its place in the market.

    Harmen,

    Sorry, I only had it in the release post, but the About pag wasn't updated. This is the DOMAssistant Team.

    I'm sure that there can be a place for you in there, but I need to think things over and evaluate how to move forward. Let's talk more over instant messaging. :-)

  • bruce says:

    Brilliant work, Mr Nyman. I shall be using it for a project in the very near future.

    Your music taste is still crap, though …

  • Chris Mills says:

    Robert's music taste is terrible, but he has a great ass.

  • @Robert; sounds good :)

    Take your time, I'll fire up MSN in the evenings and see if you're there.

  • Robert Nyman says:

    bruce,

    Thanks a lot!

    You just don't understand the music taste of the young, though… ;-)

    Chris,

    Dude, you know we agree on music! And, eh… Thanks? :-)

    Harmen,

    Usually I'm not online in the evenings, but try to catch me during the day and we'll talk. :-)

  • That's funny, usually I'm not online during the day, at work ;)

    Well, anyhow, I'm sure we'll meet up eventually :)

  • [...] DOMAssistant v2.6 – overall fastest CSS selector performance in the market. [...]

  • Christiaan says:

    Hmm, crap. Now I might have to abandon Prototype. I just finished a big project with Prototype. I choose Prototype, because I thought it was lean and mean, but now when my project increases, Prototype is starting to get slow.

    I cant believe how much faster DOMassistant is. DOMassitant is also the only one that doesn’t seem to care which browser it’s working for. I run tests with IE, FF, Chrome and Safari on a WinXP machine.

    Browser Chrome 1.0.154.42, IE 7.0.5730.13, FF 3.05, Safari 3.1.2
    DOMAssistant 2.7.4: 21,  24,  30, 4
    jQuery 1.2.6: 43,  227,  120, 48
    Prototype 1.6.0.3: 26,  1206,  194, 4
    Mootools 1.2.1: 49,  318,  110, 44
    ExtJS Core 2.2: 26,  116, 76, 8
    Dojo 1.2: 52,  452,  88, 59
    YUI 2.6.0: 186,  774,  272, 247

    These are milliseconds. Tests are performed with http://www.domassistant.com/slickspeed/

    Conclusion. DOMassistant doens’t care about the browser. It outperforms any other javascript library in any browser…big time.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>