@raggi what are some? Rails 3 worked insanely hard on compat, for example.
@raggi higher value features can tolerate more upgrade cost. Every change is a tradeoff.
-
-
@wycats right, but lets look another way too: give the project a new name, hand off old maintenance. problem? -
@raggi with a big enough community, major problem. -
@wycats its the spec that is wrong, there is no incremental path except insanity -
@raggi every future rack story I've heard has had a compat shim idea. I would be shocked if that wasn't possible. -
@wycats oh a shim is simpler yeah, but you'd lose all benefit. i'd actually do it as a server type for rack1, rather than include in 2
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.