Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The analogy here is just off. DHH might consider just saying "I have good intentions. Rails is my thing. I will ultimately make the choices but do consider feedback."

The reason the analogy is off: when was the last time you went into a restaurant and said, "i'm going to base my work/livelihood on this menu"? Never. Sometimes when I go for a meal I know what I want and I order that. Often I'm looking for an experience and I'll ask, "If the chef were going to die tomorrow what would they eat tonight?". Omakase is a formalized way to see what the chef recommends at that moment in time.

Rails is not the same as me going into a restaurant looking for a great experience at that moment. I might have a mind-blowing meal but I'm not going to base my livelihood on it.

I'm not saying that DHH or Rails are flaky. I am saying that comparing a serious tool for serious work to omakase/the whims of the chef does Rails a disservice.



DHH has long held that Rails meets his (Basecamp's) needs first, so the whims of the chef hold true. Implicit in this post was the idea that it's not the only serious tool for serious work, and if you don't like the chef's choices, you're better served in a different restaurant than complaining about the menu in this one.

Even if you've staked your career on Rails, it's important to realize it's your choice, but his framework.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: