| Merb: No code is faster than no code[1][2] | |
|---|---|
 All you need… nil you don’t | |
| Original author | Ezra Zygmuntowicz |
| Developers | Ezra Zygmuntowicz & Yehuda Katz |
| Final release | 1.1.3[3] / July 12, 2010 (2010-07-12) |
| Written in | Ruby |
| Operating system | Cross-platform |
| Type | Web application framework |
| License | MIT License |
| Website | http://www.merbivore.com |
| Repository | |
Merb is a discontinuedmodel–view–controllerweb framework inRuby, notable as a precursor to Rails 3. It brought increased focus on speed and modularity to Rails 3.[4][5] The name Merb is a contraction of "Mongrel" and "Erb".[6]
Merb began as a "clean-room" implementation[7] of theRailscontroller stack but grew to incorporate several ideas that deviated from Rails's spirit and methodology at the time, most notablycomponent modularity, extensibleAPI design, andvertical scalability. It was developed by Ezra Zygmuntowicz and Yehuda Katz. Most of these capabilities were added to Rails during the Rails 3/Merb merger.[8][9] Merb was first released at the 2008RubyConf[10] and development has since stopped; Rails 3, therefore, serves as both the successor to Rails 2 and the successor to Merb.
Merb's design attempted to address several criticisms ofRails 2:
Merb itself encompassed only the controller layer inMVC architecture, and used a suite of complementary, optional plugins together to assemble applications. The primary integration points were the web server interface, the model layer, the view layer, and controller extensions and add-ons. Merb's default application stack incorporatedDatamapper for models, ERB for views, andRack and Mongrel as the web server layer.[11][12]
Before the Merb / Rails 3 merge, Rails lacked a well-defined, documented, public API for extensions and plug-ins, leading to issues when Rails changes brokemonkey-patches performed by plug-ins. With the Rails 3 / Merb merge, Rails gained a defined public API with a test suite,[9] giving users and plugin developers a clearer, more stable API to build against, reducing plugin breakage from release to release.[8]
Some early versions of Rails received bad publicity for lack of performance, frequently due to developer confusion about ActiveRecord queries.David Heinemeier Hansson, the creator of Rails, stated that Merb re-wrote many core Rails pieces to be faster,[8] and incorporated those changes from Merb in the Rails 3 merge, promising users that "Rails 3 will get all the performance attention that the Merb guys are known for".[8]
| Implementations |
|  | ||||
|---|---|---|---|---|---|---|
| IDE | ||||||
| Applications | ||||||
| Libraries, frameworks | ||||||
| Server software |
| |||||
| People | ||||||
| Other | ||||||
