This was a presentation on why Node is better than Ruby (on Rails...we get it, you're particular about the name). This is the culmination of my life's work. I should be executed.
4. Boring stuff you might know
Built on V8 engine - Chrome
Web server platform
First release in 2009 (Ryan Dahl at Joyent)
Ideally for real-time web applications
6. Apples and Oranges
Ruby is a web framework
Node.js is a web server
How can we (meaning me) compare Ruby and
Node.js?
7. Because We (meaning me) Can
Answer: In the quest to build a better website
Ruby and Node.js are the two newest-ish
technologies and honestly PHP is boring and
.NET is a 12,000 pound elephant, that’s blind
and thinks it’s a house cat.
Note: I have no idea how much an elephant weighs.
12. Things We Can Fight About
1. Language
a. Node.js is all Javascript all the time. Front-end, back-end, middleware.
b. Ruby requires learning...well...Ruby
2. Opinion-ationatedness (my way or the highway)
a. Node.js is non/un-opinionated
b. Ruby is opinionated
3. Convention vs. Configuration
a. Node.js is configuration - you write your web server and manage all modules
b. Ruby uses convention so “out-of-the-box” it is ready to use
4. Prototyping
a. Node.js is not very good for prototyping
b. Ruby is super good at prototyping (is that a compliment?)
13. The Future
As more people start using Node.js it is
imperative we integrate the goodness of other
languages into Node.js. We (meaning me) can
learn a lot from other languages and their
particular implementations.
The biggest contribution to Node.js, in my
opinion, will come from Ruby developers by way
of making Node.js more opinionated. Being able
to create an efficient way of writing massive
amounts of Javascript and implementing modules
is the biggest hindrance to Node.js and, in my
opinion, the place where Ruby is far superior.