At the same time Rails came about there was also Nitro, another Ruby Web framework. It too used this form of MVC.
I much preferred Nitro to Rails for being more lightweight as well as more amenable to evolving from bare-bones PHP-style single-file Web apps to to large, robust sites. (It also had a notion of pipeline transformation of content that was quite slick.)
The Ruby Nitro framework more or less morphed into Ramaze.
(For those curious about Ruby Web framework archaeology dig up a 2nd edition copy of Hal Fulton’s The Ruby Way (2006) and read the Web dev section. Caveat: I wrote the non-Rails parts of that section.)
Comments
At the same time Rails came about there was also Nitro, another Ruby Web framework. It too used this form of MVC.
I much preferred Nitro to Rails for being more lightweight as well as more amenable to evolving from bare-bones PHP-style single-file Web apps to to large, robust sites. (It also had a notion of pipeline transformation of content that was quite slick.)
George Moschovitis, who created Nitro, ended up moving over to JavaScript. (https://github.com/gmosx/nitro)
The Ruby Nitro framework more or less morphed into Ramaze.
(For those curious about Ruby Web framework archaeology dig up a 2nd edition copy of Hal Fulton’s The Ruby Way (2006) and read the Web dev section. Caveat: I wrote the non-Rails parts of that section.)
Nitro and Og yo!