Re:Cutting Corners or Why Rails May Kill Ruby
by ssmoot on Saturday June 06, 2015 @09:21PM
(#9673031)
What if you could require() your patch just where you needed it? You'd have the utility and elegance of the simple solution, without abusing the global namespace.
That's exactly what you'd do in Scala.
implicit class HtmlHelpers(node: Node) {
def id: String = node \ "@id" text
def name: String = node \ "@name" text
def cssClass: String = node \ "@class" text
def href: String = node \ "@href" text
}
And I haven't abused anything. Whenever I need it, even within another method, I can just import until.HtmlHelpers.
Re:Cutting Corners or Why Rails May Kill Ruby
by capsule_toy on Saturday June 06, 2015 @08:49PM
(#9672964)
While I agree with the sentiment, I don't believe it's necessarily cutting corners. Rather, it's by design. Rails values "elegance," and leans towards monolithism. Monkey patching is the means to those ends.
So even though I agree with you, I think it's going to be very difficult changing the philosophy of the Rails' ecosystem.
[0] http://apidock.com/rails/Array/forty_two
That's exactly what you'd do in Scala.
And I haven't abused anything. Whenever I need it, even within another method, I can just import until.HtmlHelpers.So even though I agree with you, I think it's going to be very difficult changing the philosophy of the Rails' ecosystem.