3 ms·
"This was largely because merb attempted to do much the same things that Rails was trying to do, but to do them in a much better way." Or maybe because Merb wa
by jamesbritt 17y ago
"This was largely because merb attempted to do much the same things that Rails was trying to do, but to do them in a much better way."
Or maybe because Merb was done by people already hooked into the Rails community, and so could more easily get the attention of developers who don't otherwise seem interested in exploring other frameworks?
Nitro, for example, predated Merb (it came out at the same time as Rails) and was doing many things better than Rails (multi-threaded, easy to swap out ORMs, no boinking of built-in classes, Rack-like app request processing pipeline before there was Rack; much faster overall), but got almost zero traction. And I don't think it was because people tried it and didn't care for it, but because all the noise was (rather deliberately) about Rails.
There is a "winner takes all" mentality among some Rubyists that leads them to dismiss anything that isn't the clear leader. Sort of like high school kids who are afraid to be seen talking to the nerds because people might think them uncool.