31–40 of 57 posts
Impressive! How often do you hear about two open-source projects merging? Forking is much more common. I can't even recollect other instances of merging. Best of luck to the two teams with making it work!
Impressive! How often do you hear about two open-source projects merging? Forking is much more common. I can't even recollect other instances of merging. Best of luck to the two teams with making it work!
Wow, I almost wish it were April Fools Day... For someone who loves Merb and had decided to leave Rails behind (as much as possible), I have very mixed feelings about this. If this means Rails will start to feel more like Merb, fantastic! Otherwise? I have a feeling it'll be a long while before I really know how to feel about this... It'll be interesting to see how well this merger actually works in practice. It seem…
It's open source... fork it. I'm sure someone will.
Earlier quoted context omitted.
It's open source... fork it. I'm sure someone will.
Well, there are already over 400 Rails forks on github. ;-)
There's a difference between someone forking Rails on GitHub so they can say "look at me, I maintain my own fork of Rails" (like 99% of those Rails "forks") and a legitimate open source project.
Impressive! How often do you hear about two open-source projects merging? Forking is much more common. I can't even recollect other instances of merging. Best of luck to the two teams with making it work!
Impressive! How often do you hear about two open-source projects merging? Forking is much more common. I can't even recollect other instances of merging. Best of luck to the two teams with making it work!
Impressive! How often do you hear about two open-source projects merging? Forking is much more common. I can't even recollect other instances of merging. Best of luck to the two teams with making it work!
Can people stop coming up with examples? You're ruining mdemare's argument.
I'm a merbist and think this will be good for both the Merb and Rails communities.
That said, I'm a little afraid it will shaft the other Ruby frameworks (Sinatra, Camping) and possibly straight ruby too. People might make interesting things only compatible with Rails.
When Merb was a pretty big, active minority, it was more compelling to go out of one's way to make interesting libraries (ORMs, gems, etc.) easily compatible with anything ruby.
Now, people might at the least write things specifically setup for use w/ rails in such a way that it's inconvenient to nonrails ruby, and at worst make Rails plugins for things that could be useful libraries for all of Ruby.
Rails is gaining modularity, but I fear Ruby overall might lose it. Even after Rails and Merb merge, rails!=ruby.
Merb has become the 'go to' framework for Rails developers like myself who are unsatisfied with several Rails design choices.
However, the technical differences between the two are actually not that big. A merge of Merb and Rails concepts sounds like a good thing, all 'round.
Three cheers for open-source development and civil relationships between developers.