3 ms·
I think it's quite telling that DHH frequently tweets his opposition to aspects of what is happening with Rails, and that Yehuda quit the core team. In a world
by grandalf 15y ago
I think it's quite telling that DHH frequently tweets his opposition to aspects of what is happening with Rails, and that Yehuda quit the core team.
In a world where some time on the core team can land someone $300K per year in salary + speaking + book deals, there is bound to be this sort of chaos. I view the push toward agnosticism as a misguided attempt to be the "one true framework" and also to salve the egos of those whose decisions and work are being undone.
- bradleyland 15y ago"I think it's quite telling that DHH frequently tweets his opposition to aspects of what is happening with Rails, and that Yehuda quit the core team." That's a bit disingenuous, isn't it? Yehuda was offered an opportunity that makes sense for him. It's not as if he's abandoned the Rails community in a flurry of drama. DHH is the kind of guy that is going to speak his mind, and if you're wise you'll at least listen to what he has to say. If you find yourself agreeing 100% of the time, it's time to find different company.
- dasil003 15y agoYeah, did Yehuda quit so much as fade into the background? He's clearly a guy who likes ambitious projects. His contributions to the Ruby community have been notable because of their challenging nature. Merging Merb and Rails was a gargantuan project, getting a large established framework to accept that level of outside input was impressive. The level of refactoring that went into it went against prudence, but I can't argue with the results. Rails 3 is awesome. Similarly Yehuda and Carl spearheaded Bundler development. They bit off a massive problem that touches anyone doing large scale ruby development and through sheer force of will hammered out a powerful solution that solves the majority of common issues in a relatively straightforward manner. There's lots to argue with, for sure, maybe it's over-engineered, maybe they didn't work closely enough with RubyGems core, etc; but at the end of the day they solved a problem that was too hairy for the average dev to have much hope of solving. Yehuda's been there, done that. He doesn't need to stick around and be Rails core forever, there's plenty of new blood to pick up the torch, and bigger problems to solve elsewhere.
- wycats 15y agoI didn't quit the Rails Core team (http://rubyonrails.org/core http://rubyonrails.org/core). I no longer work full-time on Rails, but I've been continuing to work with other members of the Rails core team on maintaining code I wrote (most notably encoding-related code and code related to the Railtie system). I've also been contributing more code recently, and after taking something of a hiatus, have gotten back into it a bit. No drama here!
- grandalf 15y agoThat too is a relief. Thanks much for the clarification. And thanks for your tremendous contribution to open source.
- dhh 15y agoRails 3.1 is by very far the best version of Rails there's ever been. Nothing makes it in or stays in the framework if I have true opposition to it being there. Believe you me. Also, please back up your core theory with something else than wild conjecture. Core is more stable and uniform than it's been in years.
- grandalf 15y agoThat is a relief. Thanks for the clarification... and also for your great contribution to open source. Not trying to stir the pot but I felt like I had to speculate and hoped someone would illustrate that I was wrong.