rails 3 illustrates that engaging @dhh on the issue of modularity works well if you're willing to do the work.
-
-
Rails 3 was an obvious improvement, nobody denies that! You made impossible possible
1 reply 0 retweets 1 like -
your blog post implies you're angry about the collaboration to this day!
3 replies 0 retweets 0 likes -
collaboration is impossible when
@dhh can veto anything that is against his philosophy. BUT IT’S FINE REALLY!1 reply 0 retweets 0 likes -
how can you believe that and what you said about rails 3 at the same time?
1 reply 0 retweets 0 likes -
bkz I’m thinking about concrete stuff now - callbacks, validations tied to AR, tons of methods. That won’t change
1 reply 0 retweets 0 likes -
DataMapper had validations. I think it's possible to come up with a better "callback" story but work in apps is key
1 reply 0 retweets 0 likes -
the way I think about it,
@dhh has stuff he wants, I have stuff I want, and they usually don't contradict directly.1 reply 0 retweets 0 likes -
if your solution just drops
@dhh's constraints, you will not be surprised to learn he rejects it.1 reply 0 retweets 0 likes -
the fact that a solution that satisfies more than one constraint is hard is just the definition of software.
1 reply 0 retweets 0 likes
@@dhh what I usually hear: "my constraint is more impt than his, therefore I shouldn't have to find a soln that satisfies both"
-
-
that's a very good way to deadlock and feel like
@dhh is ruining Rails.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.