Honestly, I'd put you in the latter camp because you've given code to the community and promoted change.
-
"legacy" is an important word. I aim to work on software that is 3+ years old but isn't "legacy."
I'd prefer to see no one ever truly happy with an OSS project and for things to always be changing
I'm using it to refer to a large codebase that has been touched by many people. Poor choice of word, sorry
-
-
and believe me I'm not nitpicking out of being pedantic :) I really think it's in Rails best interest to understand
-
Just because some features don't affect every developer doesn't mean we don't understand the needs of others
End of conversation
New conversation -
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.