MerbCamp Closing Keynote (Ruby is Not Slow & Merb 2.0)

1. Merb
Lessons Learned & Where Do We Go From Here

2. Engine Yard

3. Ruby is slow

4. “It’s also worth mentioning that there shouldn’t
be doubt in anybody’s mind at this point that
Ruby itself is slow. It’s great that people are
hard at work on faster implementations of the
language, but right now, it’s tough.”
Alex Payne, Twitter

5. Does this discourage me from Ruby or Rails? Hell
no. To me the elegance of the language
completely dominates its flaws... I’ll wait for the
performance and scale issues to be fixed in
subsequent releases
Daniel Miessler

6. You will also find that Ruby is one of the slowest
languages in existence.
Sam (harparkrat@gmail.com)

7. quot;Ruby is slowquot;: a JIT is under development, the
VM has a lot of room for performance
improvements, and hardware keeps getting
faster. Java was slow for the hadware that
existed when it was originally created.
Luis (lcrespom@gmail.com)

8. I for one am scared of Ruby because ... it's
known to be slow, so if you become The Next
MySpace, you'll be buying 5 times as many
boxes as the .NET guy down the hall.
Joel Spolsky

9. Rails is for the vast majority of web applications
Fast Enough... I just happen to care much more
about free developer cycles and am willing to
trade the former for the latter.
David Heinemeier Hansson

10. Would you rather come to market late on the
back of an inferior development environment
(asp.net) or make it to market first with a
superior development system and work to
alleviate the scalability issues?
Jim Jones, RunFatBoy.net

11. Ruby is so embarassing.

12. To Summarize

13. Rails is slow.

14. Ruby is slow.

15. “The slowest programming language in the world”

16. Our response?

17. It’s ok.

18. I program faster.

20. WTF!

21. Someone must have done some benchmarks, right?

23. Simple, real app

24. raw PHP: 331
rps

25. cakephp: 3.6

26. with code
acceleration

27. 88 rps. With
Rails.

28. Existing results?

29. Let’s try and replicate with Merb

30. Hello world.

31. Merb

32. Merb Static HTML

33. Merb Static HTML PHP

34. Merb Static HTML PHP Cake

35. While we’re on the topic of benchmarks

36. Merb router Merb controller Sinatra Rails

37. Merb router Merb controller Sinatra Rails CakePHP

38. We don’t need to be embarassed

40. The future...

41. Merb 2.0

42. Modular

43. Integrated

44. “It’s hard”

45. Yep.

46. Django.

49. Edit Your DB (Auto-admin)

50. Admin Hooks for Slices

51. Admin Hooks for Slices (central /admin)

52. Merb ORM interface

53. Possible to build stacks with AR/Prototype

54. Mailer becomes Messenger

55. Process

56. 1.0 is a stake in the ground

57. 1.x are back-compatible, stable experiments

58. We will run the 1.0 public spec suite against 1.x releases

59. We will support 1.0 via 1.0.x

60. Once 1.2 is released, only 1.0 and 1.2 are supported
with bug fixes.

61. We will backport security patches to 1.x until 2.0.

62. Public API means extensive community involvement

63. Keep an eye on slices

64. To summarize:

65. To summarize: Merb 2.0 is about Rapid Prototyping

66. To summarize: Merb 2.0 is still metal

67. Opt-out should be granular

68. Legos

69. Legos vs. Duplos

70. Want to get involved?

71. Central slice repository

72. Work on the wiki

73. Help test RC1

74. Report missing functionality in @api public

75. Experiment

76. Report success

77. Merbunity.com:

78. Merbunity.com: List Your Site

79. Thank you!
• Carl Lerche • Andy Delcambre • Patrick Crowley
• Matt Aimonetti • Avrohom Katz • Ryan Felton
• Ezra Zygmuntowicz • Ben Burkert • Leah Silber
• Wayne Seguin • Daniel Neighman • FiveRuns
• Michael Ivey • Tim Carey-Smith • NewRelic
• Fabien Franzen • Drew Colthorp • topfunky
• Michael Klishkin • Rob Kaufman
• Paul Sadauskas • Wesley Beary

80. And Everyone Else I Missed ;)

81. Questions?