Rails + Merb == Rail3.0 == Merb2.0

I do not think so.

Rails and Merb Merge. I believe this is the worst idea from the software developer point of view.

I have no idea who is the investor for both 37s and EY. But this deal seems it all comes down to $$$. This is a business decision, which is fine. But I just can't understand why it is "such a good thing" for the community like what they advertised. Sigh...

Anyway, I had jobs to be done. I will fork the Merb, it is open source, right?

All that said, good luck with the "merge".

Integrate Ack with Vim

I've been a long time Vim user, but the searching in a project is the missing part in Vim compare to TextMate. I used to switch to a command line using 'grep' or 'rak'(a ruby gem). Finally there is good tip how to integrate it into vim: Ack plugin for Vim

Here is how I do it on my Mac:

1. Install File-Next
2. Install ack
3. Edit your vimrc, add:
set grepprg=ack

4. Create a ack.vim in your .vim/plugin/


Fire up your vim:

:Ack text_to_search_in_current_path

dm 0.9.8 breaks YAML.dump

If you are wondering why your code stop working on dm 0.9.8, this could be one of the reason:
The DM 0.9.8 breaks the after you do any operation on the result Array:


So the workaround could be:
1. Issue only one query to get all you need
or
2. If you can not do 1, then you have to get all the ids, then use (:id.in => ids) to make it working.

Hope this could save you sometime to figure out the very strange error info.

Here is the ticket on light house.

A little tiny bug in Phusion Passenger 2.0.5

If you are using Phusion Passenger like me, I believe you would love it very much. It is such an effort saver. So I've put it on all my machines, even on my dev. , testing and staging machines. But some times I want my Rack apps started in a development mode, so I went through Passenger's document, and added RackEnv environtment variable.



After a restart, I've found that the app was still in production mode. Just played with it for a while and added some debug info, finally I found a workaround, that is, put the RackEnv outside the VirtualHost block.



I am hoping this will save you some time.

P.S. I've submitted a bug report on the issue tracker