Comments on: Dispatch from the Front Lines http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/ Random Geek-Related Thoughts Sat, 20 Apr 2013 07:23:38 +0000 hourly 1 By: Beckham http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-16010 Beckham Sun, 08 Mar 2009 13:03:59 +0000 http://yehudakatz.com/?p=144#comment-16010 Я так понимаю, в последнем абзаце как раз вся соль и изложена ;)

]]> By: The Merbist » Blog Archive » latest Merb and Rails 3.0 news | Merb & Rails 3 news - consulting - training http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15245 The Merbist » Blog Archive » latest Merb and Rails 3.0 news | Merb & Rails 3 news - consulting - training Mon, 29 Dec 2008 21:57:58 +0000 http://yehudakatz.com/?p=144#comment-15245 [...] every single step and even though most people are enjoying a well deserved break, you can read the details of the work started on the [...]

]]> By: Double Shot #358 « A Fresh Cup http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15238 Double Shot #358 « A Fresh Cup Mon, 29 Dec 2008 11:50:59 +0000 http://yehudakatz.com/?p=144#comment-15238 [...] Dispatch from the Front Lines – And Yehuda Katz is also writing about the work to come. The more of this sort of thing we see from the merged team, the less FUD there will be to go around. [...]

]]> By: Weekly Digest, 12-28-08 - almost effortless http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15235 Weekly Digest, 12-28-08 - almost effortless Mon, 29 Dec 2008 04:33:54 +0000 http://yehudakatz.com/?p=144#comment-15235 [...] Dispatch from the Front Lines It’s been a very busy few days, but I’m glad to say that the work on the Rails/Merb merge is going quite smoothly. Some things that have already happened… [...]

]]> By: Yehuda Katz http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15209 Yehuda Katz Sat, 27 Dec 2008 12:14:52 +0000 http://yehudakatz.com/?p=144#comment-15209 @botanicus you will still be able to use case content_type as in Merb. This is a replacement for display, and will not require the creation of any new blocks.

]]> By: Botanicus http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15205 Botanicus Fri, 26 Dec 2008 21:10:19 +0000 http://yehudakatz.com/?p=144#comment-15205 David hasn’t permitted comments, so at least here:
1) congratz to provides/display, BUT
2) that’s pretty bad idea to have respond_to block when it can be done more rubyish and more faster and logic through case content_type as is in Merb.

]]> By: Alistair Holt http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15204 Alistair Holt Fri, 26 Dec 2008 21:04:04 +0000 http://yehudakatz.com/?p=144#comment-15204 Looking good :)

]]> By: Jay Levitt http://yehudakatz.com/2008/12/26/dispatch-from-the-front-lines/comment-page-1/#comment-15202 Jay Levitt Fri, 26 Dec 2008 15:45:01 +0000 http://yehudakatz.com/?p=144#comment-15202 This is heartening. The hardest part of merging two codebases – and two cultures – is the endowment effect. We did X this way, we’re sure we did it this way for a good reason. We worked hard, it’s already done and it finally works, and we’re certainly not going to revisit that whole discussion just to work with your code.

You’re taking the opposite approach: We did X this way. We were never thrilled about it, but it had the best set of trade-offs at the time. Do you have a better way to do X? Does the merge eliminate the need for some of those trade-offs? What do your fresh eyes see in X?

That’s a teaching moment for the rest of us.

]]>