Here's my .irbrc file. This is based off of this post by Thoughtbot about using wirble with your IRB.
This gives me auto-completion, history, color, Rails SQL output and a few other conveniences.
Wednesday 24 December 2008
On the Rails merger with Merb
I think overall it will be a good thing.
There obviously are a lot of common goals between the two frameworks but I'm more interested in how they merge some of the more controversial differences. Both teams have already mentioned modularity and internal APIs as something that Rails is going to adopt, but what about some of the smaller differences?
Some of the more difficult issues to be resolved might be:
I'm certainly looking forward to seeing what they come up with!
There obviously are a lot of common goals between the two frameworks but I'm more interested in how they merge some of the more controversial differences. Both teams have already mentioned modularity and internal APIs as something that Rails is going to adopt, but what about some of the smaller differences?
Some of the more difficult issues to be resolved might be:
- Merb's requirement for an explicit call to render or display - will that be optional?
- Merb's mailer and exception handling - Merb way is probably superior
- Rails' extensive use of monkey patching and magic versus Merb's preference for code simplicity
- Rails' use of test/unit versus Merb's RSpec preference - will all of rails internal tests be rewritten in RSpec?
- slices versus engines - support both??
I'm certainly looking forward to seeing what they come up with!
Subscribe to:
Posts (Atom)