Paradox of choosing "progress" over "stability" is that it actually slows things down. Both is harder, but the only way to sustained speed.
@raggi the fail cases are predominant. Success is rampant: C++, ObjC, Java 8, Ruby 1.9.2. 100% compat not required; just incremental moves
-
-
@wycats if it was possible to break the pointer API restrictions in MRI, the GC could improve 10x or more -
@raggi MRI is doing this incrementally. Shady objects. Move the community. This is what I'm talking about. -
@wycats spreading out breakage over many many years only hides it. pretending that isn't actually happening as a result is a fallacy -
@raggi big deny. Communities move at their own pace. Rush it and you fail. -
@wycats i agree it's important to manage community workload, and if you put too much on, people walk. but that happens anyway, e.g. ruby
End of conversation
New conversation -
-
-
@wycats well sure, but we can also list a ton of places where major things could be improved in each of those if more was broken -
@raggi yes, that's what Perl 6, Python 3, PHP6, Plan 9, XHTML, ES4, all thought. It doesn't work. -
@wycats xhtml seems like an exception in that list, it seemed to go ok -
@raggi very low adoption, HTML5 ignores />, browsers treat it like a black sheep. -
@wycats you say that, but i'm constantly sending patches to remove xhtml-isms :D
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.