991 karma · joined September 16, 2010
I get what you're saying, but I don't think it's as important that Louisville be the "best" in any one of those categories so much as "sufficiently good".
It's like Maslow's hierarchy of needs. Satisfaction at one tier opens up the others.
Cultivate relationships in whatever form they take.
Nitpicky, but ActiveRecord::Relation is not ARel. ARel is the relational algebra library that underpins ActiveRecord (>=3.0). See http://erniemiller.org/2010/05/11/activerecord-relation-vs-a... for more info.
The specific example he used to demonstrate worked transparently because of the has_many :through relationship for users on Article, which requires the collaborations table to filter the users, so joins it. Otherwise, you would need to do the join yourself before merging the scope, and things get messy pretty quickly, especially if you end up with table aliases (which the merged relation knows nothing about -- it will still query against the collaborations table).
I added "sifters" to Squeel (http://github.com/ernie/squeel) in order to address the need for a set of reusable conditions on a specific model that could work through an association. I'm not saying Squeel is the solution you're definitely looking for, but I just want to let people know about the things they'll need to look out for when using Relation#merge.
I think there's probably a significant correlation of 37s product users to HN users, but if there's any causation to be found here, it's likely in the direction of explaining why these posts get frontpaged, not in how these frontpaged posts lead to indirect sales.
ORMs don't kill databases. Hacker News does.
I'm nobody special, to the Ruby community, so I'm not going to claim my opinion carries a lot of weight, here. That being said, you have to see how characterizing Loren's work as a "hostile fork" isn't the most neutral thing to say.
It would appear to me that you've definitely moved past the role of mediator, but when you say things like "I must at least strongly consider the opinions of the current maintainers of RubyGems" it sounds as though you're now casting yourself in the role of judge, instead.
You're doing great things with RMU -- we thank you for it, and I'd hate to see the fallout from the role you're attempting to play here overshadow your great contributions to our community thus far.
(Re: "Identify your target customer. COLD email 20 of them and offer to pay THEM to use your product if they are willing to offer some feedback. See how many respond. If anybody responds, tell them that the offer is oversubscribed and that it is no longer available. See how many of those people still ask about the product.")