@elskwid AFAIK rails code / feature base makes it uneasy to be backwards compatible.
-
-
@wycats@dhh@steveklabnik@fxn every bug that someone works around is someone else’s feature, the distinction’s academic and pointless -
@nzkoz I'm amazed to hear you say that. Thinking about it for 2s is a worth exercise.@dhh@steveklabnik@fxn -
@wycats@dhh@steveklabnik@fxn it’s a worthy stretch goal, but you tell me how it prevents this:https://github.com/blog/1440-today-s-email-incident … -
@nzkoz it's not about preventing everything, just having a process for thinking about it.@dhh@steveklabnik@fxn -
@wycats@dhh@steveklabnik@fxn I’m only arguing against the idea that picking magical numbers helps, everything breaks, people fuck up, sux -
@nzkoz magic numbers are silly, but a bit more thinking before making changes wouldn't be bad.@dhh@steveklabnik@fxn -
@wycats@dhh@steveklabnik@fxn yep, 100% agreed. GitHub makes back porting too painless -
@nzkoz Rails has a lot of contributors, which is good, but I see a lot of cosmetic changes that unnecessarily break things - 2 more replies
New conversation -
-
-
Thanks. 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.