A look at the history, current state, and hopeful future state of script loading in browsers.

1. The Once and Future Script Loader Kyle Simpson @getify http://getify.me

2. where… we were we are now we’re going next

3. where…we were once upon a time, in a browser far, far away…

4. <script src=&quot;…&quot;></script> where…we were

5. <script src=&quot;…&quot;></script> where…we were <script src=&quot;…&quot;></script> <script src=&quot;…&quot;></script> <script src=&quot;…&quot;></script> <script src=&quot;…&quot;></script> <script src=&quot;…&quot;></script> …

7. where…we were <script> tags block. bad. evil.

8. where…we were IE7-, FF3-, Chr 1...

9. where…we were IE8, FF3.5/3.6, Chr 11-

10. where…we were IE9, FF4 Script Loaders

12. where…we were document.write()

13. where…we were document.write() Must Die!

15. So, we need a script loader, huh? where…we were

16. where…we were The very first script loader? document.write(&quot;<script src='...'></sc&quot;+&quot;ript>&quot;);

17. where…we were w ho- tf ? ...and still many ad providers, 3rd party widgets, etc.

18. Other attempts at script loading where…we were

19. where…we were Loading script in <iframe>? ugh. What about with XHR?

20. where…we were Making progress... but not there yet

21. where…we were Framework-specific loaders... ...just stink

22. where…we were Not for the faint of heart

23. General Script Loaders (1st gen) where…we were

27. A young leader? LABjs where…we were

28. LABjs: performance script loader where…we were

29. where…we were LABjs: performance script loader

33. Anyone can write a loader! where…we are now (and many devs have)

34. where…we are now https://spreadsheets0.google.com/spreadsheet/ccc?key=tDdcrv9wNQRCNCRCflWxhYQ

35. Loaders are competing more on APIs than on features or performance where…we are now

36. But, can their functionality be trusted? where…we are now

37. where…we are now Testing is much harder than you (and they!) probably realize

38. where…we are now &quot;Browser support&quot; is not a universally agreed upon measurement

39. where…we are now Exception cases are either ignored or overlooked, more than they admit

40. where…we are now Functionality based heavily on hacks and browser sniffs, not feature detects

41. where…we are now End users have no clue, they trust what the docs say

42. Appears friendly and civilized where…we are now

43. Actually ugly and dangerous where…we are now

44. What happens now? where…we're going next

45. Competition is good, only if community is educated on what to look for where…we're going next

46. http://Pick A Loader.com where…we're going next

47. The browser doesn't yet give us what today's web needs for script loading where…we're going next

48. Co-opetition is much healthier for the future of script loading where…we're going next

49. Only script loaders which participate in defining the future will survive where…we're going next

50. W3C, WHATWG where…we're going next http://wiki.whatwg.org/wiki/Category:Proposals

51. async=false where…we're going next http://wiki.whatwg.org/wiki/Dynamic_Script_Execution_Order

52. We'll accomplish more if we work together where…we're going next

53. Advanced Script Loading where…we're going next

54. Preloading where…we're going next (deferred execution)

55. Modules where…we're going next (CommonJS, AMD, etc)

56. Native Modules where…we're going next (ES-Harmony?)

57. &quot;Script Loader of my dreams&quot; where…we're going next

59. True Preloading where…we're going next http://wiki.whatwg.org/wiki/Script_Execution_Control

60. IE4+ ftw? where…we're going next

61. What else...? where…we're going next

62. And now for something completely different... Questions?

63. http://pickaloader.com Kyle Simpson @getify http://getify.me http://labjs.com http://wiki.whatwg.org/wiki/Category:Proposals