Skip to main content

JS Performance

How DRY impacts JavaScript performance // Faster JavaScript execution for the lazy developer presentation by: Mathias Bynens



http://speakerdeck.com/u/mathiasbynens/p/faster-javascript-execution-for-the-lazy-developer

In my opinion most important is to write maintainable code and optimize only what needs to be optimized.
http://speakerdeck.com/u/mathiasbynens/p/faster-javascript-execution-for-the-lazy-developer?slide=49

Comments

  1. Ciekawe podejście.

    Szczególnie interesujące wydaje się wywoływanie switcha jako obiektu.

    Będę musiał sprawdzić, o ile jest to szybsze od zwykłego switcha.

    Jeśli jednak chodzi o rozwiązania w stylu
    $('.aaa').length zamiast $().size()

    to mam mieszane uczucia. Nie sądzę, aby przyspieszenie było aż tak wielkie. Natomiast ryzyko tego, że kiedyś cokolwiek się zmieni i to size() będzie czymś więcej niż tylko prostym zwróceniem length wydaje mi się wystarczająco duże (nie mówię akurat, że nagle kolekcje w JS stracą takie pole, ale ogóle jestem zdania, że lepiej jest wywoływać metodę, niż pole wprost).

    ReplyDelete
  2. Ja bym nie przesadzał jeśli chodzi o optymalizację. Kod powinien być po pierwsze łatwy w utrzymaniu.
    Jeśli chodzi jednak o .length zamiast .size() to w przypadkach gdy jakaś funkcja jest wywoływana bardzo często, powiedzmy mainloop gry, czy w setInterval itd. może to mieć znaczenie.

    Powyższe w większości stosował bym tam gdzie jest konieczne choć trzeba przyznać, że niektóre z nich są tak oczywiste, że nie ma powodu by nie stosować za każdym razem :)

    var utilFun = lib.ro.util.superFun;
    utilFun(1);
    utilFun(2);
    utilFun(3);
    utilFun(4);

    będzie bardziej czytelne i szybsze niż wersja dłuższa.
    PS. (No chyba że to IE9? :)

    ReplyDelete

Post a Comment

Comments:

Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Length:
Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…