3 ms·
And this is why people reinvent the wheel. If you disagree with the core teams decision here, you are at an impasse. So, you fork and move on. Or, you think a
by jasonlotito 15y ago
And this is why people reinvent the wheel. If you disagree with the core teams decision here, you are at an impasse. So, you fork and move on. Or, you think about it, and decide to create your own framework that will be like Rails, but do things the way you want to do them, including making xhr? work the way you think it should.
Reinventing the wheel gets a bad wrap. People suggest you should contribute to existing projects. The problem is when that existing project's direction diverges from your needs. Reinventing the wheel is part of the power of open source.
On a side note, considering the sheer number of types of wheels, "reinventing the wheel" comes across as a bit odd.
- dhh 15y agoThis is exactly the point of the original post. That if you're willing to redo Rails because a predicate method does not return singletons, you're a rookie who don't know the value of time. Of course, people don't actually do this. They talk about doing it, but don't actually carry through.
- jasonlotito 15y ago> That if you're willing to redo Rails because a predicate method... I wasn't clear. My mistake. The issue isn't one of a predicate method, but rather, overall approach. If Rails doesn't work the way you want, you don't whine and complain it doesn't work. You either accept it, or move on and do something better. The if the attitude demonstrated here is something you can't work with, you move on. It's not just this issue, but every issue like it as well. I agree with the premise of the post (bike shedding is pointless); however, if you need a garage and not a bike shed, trying to get people who want that bike shed and are building that bike shed to instead build a garage, your better off moving on.