4 ms·

So, I posted this on one of the threads for other blog posts about this, but that tread doesn't have much going on, and I want to see what people have to say ab

So, I posted this on one of the threads for other blog posts about this, but that tread doesn't have much going on, and I want to see what people have to say about it: 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.

mileszs 18y ago
There are plenty of people in the Ruby community who avoid Rails (whether their reasons are valid or not). I think you'll find plenty of Rubyists who wish to create things outside of Rails. Whether that means they will be throwing weight behind another framework such as Ramaze, or creating a new one, I can't say. I do believe that there are enough anti-mainstream hackers in the mix now that you don't have to worry about that "scene" dying. You're one of them, to an extent, and there's nothing wrong with that. Have at it.