I think that the Rails team should be able to accept some argumented criticism. But they usually discard it.
-
-
For example,
@sgrif also got insulted by my ActiveRecord criticism, and called it "bile" even though it was well-argumented.1 reply 0 retweets 1 like -
Replying to @jankomarohnic
happened to me too, sadly, as I respect the guy a lot, he’s super smart and talented
2 replies 0 retweets 1 like -
Replying to @_solnic_
Asking to tone down the rhetoric != getting offended. I simply thought the "Rails is done because supress exists" comment silly
1 reply 0 retweets 5 likes -
Replying to @sgrif
it’s “done” as in it’s owned by DHH practically speaking. Rails core people have little influence on decision making.
2 replies 0 retweets 4 likes -
In my years working with
@dhh, I never saw him shy away from a vigorous debate around dissenting opinions.6 replies 3 retweets 11 likes -
"influence" on Rails core largely comes from (1) doing work, (2) empirical facts. It's not always fun but it works imo
1 reply 3 retweets 12 likes -
And 3) A/B'ing real code against proposed methods and architectures
1 reply 1 retweet 6 likes -
that’s the thing man, your basecamp-as-a-metric approach hurts rails, this is no longer 2005
9 replies 0 retweets 7 likes -
So I expect Yehuda to ground arguments in Skylight. Rafael in Shopify. Aaron in GitHub. Me in Basecamp.
1 reply 1 retweet 4 likes
indeed. I follow this general principle in Ember too and it works well. "Show me the code"
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.