Life after jQuery

Life after jQuery

How Yell removed jQuery from its mobile site, and how it changed how we develop our JS. First presented at Oxford Geek Night 40

2fdb5b62030270813e22f5e17d16f6b9?s=128

Steve Workman

May 13, 2015
Tweet

Transcript

  1. Life after jQuery

  2. Steve Workman • London Web Standards Organiser • Lead UI

    Engineer @ Yell @steveworkman @webstandards
  3. You May Remember us from…

  4. @leonardogrecoLG #Vintage or what? This @yell #BOOK was delivered @7.30am!

    Haven’t seen one in ages. Goes well with the period phone! “
  5. Smartphone != Xbox Flagship mobile phones aren’t up to 1/3

    of the power of last- gen consoles Kraken 1.1 (lower is better) Samsung Galaxy S6 – 3993ms My laptop – 1043ms jQuery is significantly slower than native code http://jsperf.com/comparing- jquery-and-native-js/11 https://jsperf.com/jquery-vs- native-element-performance
  6. grasp  '$(__).__'  -­‐e  -­‐o  *.js |  sed 's/.*[.]//'  |  

    uniq -­‐c.  
  7. Three months later

  8. Bounce rate on top 3 smartphone pages during release window

  9. None
  10. Bugs • IE10 doesn’t support dataset – use .getattribute(data-prop) •

    Jasmine-jQuery (fixtures) – clash of namespace • Re-named $ to QSA – complete re-write • Lots of complex logic, .bind/$.proxy • It’s not simple, bugs happen
  11. Compromise

  12. Progressive Enhancement Wins

  13. None
  14. Thank you Follow Me: @steveworkman Slides: speakerdeck.com/steveworkman Yell is Hiring

    – careers.yell.com