Brûlons les musées

Transcript

1. Brûlons les musées @fat Apr 2012
2. I work at twitter
3. I write libraries
4. Bootstrap Ender Hogan
5. I sometimes read books
6. Futurism and Dada
8. Eliminating the past
9. Early 20th Century telephones automobiles airplains
10. We affirm that the world’s magnificence has been enriched by a new beauty: the beauty of speed. Filippo Marinetti
12. Italian Anarchists with bombs
13. Destroy everything that is past, and amidst the wild ecstasy of destruction, let man be reborn as a child, a hero, and a free denizen of the future. Dezso Szabo
14. The Great War or The End of Futurism
15. Then there was dada
17. WWI and Zurich, Switzerland
18. Not relieved. Furious.
19. Cabaret Voltaire and Hugo Ball
21. We should burn all libraries and allow to remain only that which everyone knows by heart. Hugo Ball
22. But I write libraries...
23. Why would he say that?
24. The end of prehistory and the start of history.
25. a futurist sentiment?
26. The Programming Library
27. Wexelblat, Richard (1981). History of Programming Languages
29. I’d whistle at Dick and say, “Can I have your sine subroutine?” and I’d copy it out of his notebook. Grace Murray Hopper
30. As early as 1944 we started putting together things which would make it easier to write more accurate programs and get them written faster. Grace Murray Hopper
31. Wheeler, Wilkes, and Gill designed a set of subroutines for a computer before it was implemented, and there was for the first time an available set of mathematical subroutines which were more or less standardized in the way you put data into them and the way you got data out of them, and made it possible to begin to write programs a little more rapidly. Grace Murray Hopper
32. As I went along in the process of standardizing the subroutines, I recognized something else was happening in the prgramming group. We were using subroutines. We were copying routines from one program into another. Two things wrong with that: programmers are lousy adders. Programmers are lousy copyists (B’s turned into 13’s, 4’s into A’s). It therefore seemed sensible instead of having programmers copy the subroutines, to have the computer copy the subroutines. Out of that came the A-0 compiler. Grace Murray Hopper
33. hugo ball + 1/2 century = programming libraries
34. We’ve been using these “libraries” for about 50 years
35. What if we really started over?
36. Jacob Thornton @fat 22 Feb New Interview question: You have 45 minutes to write jQuery from scratch. Get as far as you can. Start from wherever you’d like.
37. Rey Bango @reybango 22 feb @fat You’re sssssooo evil :)
38. Instinctually you’d say we’re screwed
39. The whiteboards would also suggest we’re screwed
40. But what if we just tried it anyways
41. First Attempt Qwery Bean Bonzo
42. smaller, more focused apis
43. Horse ebooks @horse_ebooks 15 mar (Dalton) Dangerous at all Times and Usually Wholly Unnecessary.
44. Usually Wholly Unnecessary
45. Turns out it’s really hard to just start over
46. particularlly when starting only from what you know by heart
47. Is there a path forward?
48. yeah bro tests!
49. Second Attempt hogan.js
50. Mustache doing it right \o/
51. improved perf + smaller lib size all around
52. mustache.js changes their ways
54. Why would Hugo say that?
55. Because things get better for everyone
56. Why aren’t we sharing all our tests? Why is this not a thing?
57. selector engines? dom utilities? less? events? xhr? futures? etc.
58. What if going forward we defined a library not by it’s implementation, but by it’s test suite?
59. We should burn all “libraries” and allow to remain only their test suites. @fat
60. thank you <3