Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Is Node.js better?

A8e44ce1b57c2689d5a7172d15df42b5?s=47 brixen
April 04, 2012

Is Node.js better?

How do we resolve the question, "is this better than that?" This talk discusses ideas for improving how we handle conflict in the programming community through the lens of evaluating whether Node.js is better than other technologies like Ruby.

A8e44ce1b57c2689d5a7172d15df42b5?s=128

brixen

April 04, 2012
Tweet

Transcript

  1. Is Node.js better? JSConf 2012 Brian Ford @brixen

  2. None
  3. oneʼs excess is anotherʼs moderation

  4. None
  5. None
  6. Rubinius RubySpec

  7. Why do I care about Node.js?

  8. Organizations tend to perpetuate the problem they were created to

    solve
  9. 10 kinds of people: 01. fear change 10. create change

  10. sub·ver·sive /səbˈvərsiv/ noun: You

  11. contrast is conflict

  12. MINASWAN

  13. controversy is entertaining

  14. shootout fight throw down

  15. advocacy is criticism criticism is advocacy

  16. Fanboi Troll

  17. We suck at conflict

  18. How can we improve?

  19. benchmarks

  20. science

  21. Your Creative Power Alex Osborn 1948

  22. alone vs group

  23. brainstormers debaters free organization

  24. Broadway Musicals and the Q factor

  25. Groupthink: The Brainstorming Myth Jonah Lehrer New Yorker 30 Jan

    2012
  26. None
  27. Thinking Fast and Slow Daniel Kahneman Farrar, Straus and Giroux

    © 2011
  28. bacon

  29. 23 x 47

  30. Programming is a behavioral science

  31. Research Methods: the basics Nicholas Walliman Routledge © 2011

  32. Validity

  33. meta-physics nature of the universe

  34. epistemology theory of knowledge

  35. people are selfish lazy easily bored

  36. scarcity

  37. Concurrency

  38. every possible interleaving of program instructions

  39. P is a program x is a routine P runs

    x x waits P waits
  40. concurrency: time state transitions

  41. suspend / resume cooperative multitasking

  42. time slice pre-emptive multitasking

  43. justifications for using Node.js

  44. J(X) > J(Y) Xʼ ≡ X Yʼ ≡ Y J(Xʼ)

    > J(Yʼ)
  45. same language on client and server

  46. there are many Javascript programmers

  47. Node.js is more fun

  48. Controversy

  49. Node.js rejects reality

  50. entire ecosystem of tools and libraries must be built

  51. Node.js will reproduce last 15 years of Ruby mistakes

  52. Passenger Cluster

  53. process concurrency is doomed

  54. symmetric errors chain of evidence

  55. Celluloid https://github.com/celluloid

  56. Thank you!