<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Merb on Scholion</title><link>https://scholion.thluiz.com/tags/merb/</link><description>Recent content in Merb on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 07 Jul 2014 14:31:20 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/merb/index.xml" rel="self" type="application/rss+xml"/><item><title>The Rails/Merb Merge In Retrospect</title><link>https://scholion.thluiz.com/notes/rails-merb-merge-in-retrospect/</link><pubDate>Mon, 07 Jul 2014 14:31:20 -0300</pubDate><guid>https://scholion.thluiz.com/notes/rails-merb-merge-in-retrospect/</guid><description>The post argues that the Rails/Merb merge delivered limited practical modularity, took too long, and left Rails behind newer web development needs while community pressure and design choices pulled in different directions.</description></item></channel></rss>