4 ms·
"This is good stuff. I certainly hope frameworks like ramaze stick around and gain their own niche market share. ... I had to get away from Rails. In fact, if
by jamesbritt 18y ago
"This is good stuff. I certainly hope frameworks like ramaze stick around and gain their own niche market share. ... I had to get away from Rails. In fact, if other frameworks like Merb, Ramaze, datamapper, and Sequel didn't show up, I would have had to dump ruby."
It's a tough sell in the mainstream Ruby (ie. Rails-centric) community. For example, at MtWest RubyConf two years ago, Chad Fowler told the assembled crowd that people working on Nitro (arguably the forerunner of Ramaze, and an influence on other Ruby Web tools) to stop. Flat out stop working on it. "We don't need it; it's just like Rails." Which, of course, was simply untrue. (My take was that Nitro was to Rails as Ruby is to Python. Similar, but with enough differences to matter. Ramaze follows in that way. Ramaze is opinionated software that says your opinion matters )
Fortunately, people kept on with developing new Web frameworks (both Rails-like and not), but none have had the same level of hype and business backing as Rails. Merb gets some decent attention, perhaps because it's (sort of) Rails-lite or Rails-done-better. (I'm not trying to disparage Merb, just offer an idea on why it gets more traction than, say, Ramaze.)
Seeing almost every 3rd-generation Ruby Web framework use Rack is encouraging, as is the continued lack of coupling to any particular ORM, and I expect to see even more loosely-coupled, easily assembled Web tools to come along.
Good times.