20. No need to require?
• Sounds nice at the beginning
Monday, November 12, 12
21. No need to require?
• Sounds nice at the beginning
• But then it starts to creep on you and
everything becomes sllllowww...
Monday, November 12, 12
22. No need to require?
• Sounds nice at the beginning
• But then it starts to creep on you and
everything becomes sllllowww...
• Slow boot time
Monday, November 12, 12
23. No need to require?
• Sounds nice at the beginning
• But then it starts to creep on you and
everything becomes sllllowww...
• Slow boot time
• Slow specs
Monday, November 12, 12
24. No need to require?
• Sounds nice at the beginning
• But then it starts to creep on you and
everything becomes sllllowww...
• Slow boot time
• Slow specs
• Slow everything
Monday, November 12, 12
25. Solution?
Spork (Zeus?)
Monday, November 12, 12
26. Solution?
Spork (Zeus?)
Monday, November 12, 12
39. Wrap up
• Use Rails, but remember there are other
things out there
Monday, November 12, 12
40. Wrap up
• Use Rails, but remember there are other
things out there
• Use Rails “carefully”, as your project grows
Monday, November 12, 12
41. Wrap up
• Use Rails, but remember there are other
things out there
• Use Rails “carefully”, as your project grows
• Don’t forget that not everything is a nail
Monday, November 12, 12
42. Wrap up
• Use Rails, but remember there are other
things out there
• Use Rails “carefully”, as your project grows
• Don’t forget that not everything is a nail
• And most important: keep using Ruby. It’s
awesome
Monday, November 12, 12
44. • Architecture The Lost Years
• Wrangling Large Rails Codebases
• Hexagonal Rails
• Celluloid
• JRuby
• TorqueBox
• About concurrency and the GIL
• Images taken shamelessly from Google.
Monday, November 12, 12