Header left Header right
 

What’s that in the waves? Oh, it’s a new Ruby framework: Waves!

Published: February 29th, 2008

There’s a new light-weight framework in the midst of the internet waves, and it’s name happens to be “Waves”.

Those that went to RubyConf1 probably heard of Waves, but if you haven’t, it’s now officially time that you do. Waves2 is now in beta and licensed as MIT (Just like Rails). Waves proclaims it’s the “next-generation” in frameworks, and is a succeeder to where Rails left off.

My Quick Opinion

It’s my belief that the latest craze of frameworks built on Rack are more or less useless and “wannabe” Merbs3. Take that offense with a grain of salt if you happen to be one of the owners of those frameworks. By useless, I mean, there’s just nothing that impressively cool or different between emerging frameworks that makes me want to use them. Merb is the only one in the spotlight besides Rails that I really give a damn about, and manages to shine. This brings me to Waves; I actually feel a bit different towards this framework because it’s built on a next-generation goal instead of what’s already being done. When a framework exhibits new ways to solve issues in an easier manner, that’s when the framework is successful and deserves a spotlight. I believe that Waves is definitely in the right direction to receive this spotlight.

Enough of my damn opinion

Let’s get to the nitty-gritty:

waves

Luckily, Waves is heavily documented, has a screen-cast, and even a tutorial by provided by the author Dan Yoder.

You can read an interview here with the author.

Waves is supposedly “thread-safe”, and according to a comment by Ezra, it’s basically the same thing that Rails employs. I’m not really sure what to say about this matter as I’m not technically knowledgeable to give facts about this. If anyone could further contrast the difference that would be excellent.

Something that I find very interesting with Waves is how it maps requests to a lambda instead of a controller / action. This is part of the “next-generation” thinking that Dan is touting.

I am planning on playing with the framework over the weekend. If anyone would like to join me, we can have a coding session over IRC.

If anyone’s already played around with Waves, how do you feel about it?

  1. RubyConf is a conference where Ruby fanatics like myself like to gather once a year. http://rubyconf.org/ []
  2. A self-proclaiming “next-generation” Ruby framework: http://rubywaves.com/ []
  3. Merb is a light-weight Ruby framework: http://merbivore.com/ []

“wannabe” merbs ? I take that as a complete joke! Merb is probably the biggest “Rails” wannabe ! Go to #merb and you’ll see “rails” every 3 lines ;-)

gravatar

Thanks for acknowledging our attempts at innovation. I look forward to your thoughts on whether we succeeded or not.

By the way, I’m in LA as well …

gravatar

Pratik: Merb is Rails done right, imo.

gravatar

[...] Waves! (tags: ruby webdev) [...]

Enter your comment

Ready. Set. Go.

In terms of the formatting, you're allowed to use markdown, textile, or basic html; it's truly up to you -- what strikes your fancy?

You don't have to worry about your e-mail address being sold to a russian-spam-mafia. I'm only going to use it for my own weird needs; like asking you out for a date on a lonely night of coding.