| ▲ | foysavas 5 hours ago | ||||||||||||||||
I wrote a book on Merb and was an active contributor. Before that I had developed several apps with Rails. That said, the Rails vs Merb era was mostly good natured competition and I don't view the Rails vs Merb period as itself having been problematic. Merb devs believed we could make app development both simple to start (as a single file like Sinatra) and easy to evolve (into a modular codebase with Rails-like conventions). Existing outside of the Rails ecosystem allowed Merb to pursue that distinct vision. The Merge between Rails and Merb, accreted many of Merb's modular architectural enhancements to Rails, but sadly deprecated the overall Merb vision. To me that was a shame, but I still wouldn't describe any of it as toxic. | |||||||||||||||||
| ▲ | leakycap 4 hours ago | parent [-] | ||||||||||||||||
> I wrote a book on Merb and was an active contributor. It might be a situation where you see it differently because you were involved or benefiting from the way things unfolded > That said, the Rails vs Merb era was mostly good natured competition [...] wouldn't describe any of it as toxic Competition can be healthy, Rails vs Merb was anything but. Quotes from Yehuda himself: ••• "I was just so blinded by tribalism that I never even bothered to check how fundamental the disagreements really were." ••• "waging an all-out war against Ruby on Rails from inside of a company that makes its money selling Ruby on Rails deployment is a pretty bad life strategy" ••• "It's so easy for our brains to turn disagreements about priorities into value conflicts. It takes a lot of effort to see past that mistake." | |||||||||||||||||
| |||||||||||||||||