Comments on: Status Memorandum

By: Hello Merb - casperfabricius.com

Hello Merb - casperfabricius.com — Thu, 01 Jan 2009 15:47:47 +0000

[...] I wish I could claim to have been playing with Merb for a while and have some real insight into the framework, but to be honest, I haven’t. I still think this a very interesting news, though, and in my opinion this can only be good news for the Rails community. Already, the brilliant Merb guys are optimizing and improving Rails, for instance this 8% speed boost in using respond_to. [...]

By: David Burry

David Burry — Thu, 01 Jan 2009 01:06:55 +0000

Regarding the 0.2ms improvement here and there, the biggest win isn’t the performance gain per se in cases like this, but the restructuring itself.

When code is well structured and optimized it makes happy programmers because:

* it’s easier to understand and work on, and that’s what drew most of us to Ruby to begin with, so obviously that’s important to all of us.
* As a welcome side effect such optimizations also mean less bugs and gotchas maintaining going forward,
* and a bit of performance gain too whee.
* And of course there’s the sense of beauty and pride when code is well organized and optimized instead of slightly messy. Like picking up the dirty socks off the floor before friends come over to visit. ;o)

So again, thanks for all your great work on this.

By: Charles Oliver Nutter

Charles Oliver Nutter — Sun, 28 Dec 2008 05:52:13 +0000

Great looking JRuby numbers :) Here’s hoping this is the year we’re finally able to make JRuby the fastest way to run Rails.

By: Maik Kempe

Maik Kempe — Sun, 28 Dec 2008 01:50:25 +0000

Thanks for your great work and sharing. 2009 will be so awesome!

By: wycats

wycats — Sun, 28 Dec 2008 00:23:47 +0000

@teamon it doesn’t feel like Rails patching to me. It feels like finding a way to incorporate the Rails DSL into the way Merb does things (while keeping it performant). The specific contours of it will depend on how performant we can make respond_to (I have some really good ideas for how to make the overhead almost nil).

By: teamon

teamon — Sat, 27 Dec 2008 23:05:06 +0000

Well, that is a option.
Last thing (i go to bed ;p) – it looks like rails3 will have saveral public APIs for some case and i`m not sure if thats a good idea.

While it looks like rails-patching i still hope rails3 will be awesome…

By: wycats

wycats — Sat, 27 Dec 2008 23:00:49 +0000

teamon: Someone recently proposed format.any(:js, :html) { #stuff }. I think that’s a worthy proposal and I suspect it’ll make it in.

Keep in mind that the old case syntax will still work and I’ll be working on a few inconsistencies in the way it works to make sure everything is works great.

By: teamon

teamon — Sat, 27 Dec 2008 22:52:56 +0000

But what about having same #stuff for several content_types ?

By: wycats

wycats — Sat, 27 Dec 2008 22:33:00 +0000

teamon: in that case, content_type will never be :my_own_content_type in Merb (because content_type is the first provided content-type that is also Accepted).

By: teamon

teamon — Sat, 27 Dec 2008 22:23:24 +0000

backward compatibility is gonna kill you…

btw, what about

def action
only_provides :xml, :json
case content_type
when :xml, :html, :my_own_content_type
#stuff
when :json
#stuff
end
end