Well, but we definitely see this in the library space as well, even below 1.0.
I wonder if some of this comes from the "we should never have a 2.0" mindset. Since anything we stabilize will be there "forever", there might be more worry about how well it will last
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Looking back in 10 or 20 years it might look like the right thing that things moved so slowly. Not entirely fair to compare it to C++ as it has the whole ISO bureaucracy but it certainly struggles with legacy features these days.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Unfortunately, the over-caution applies even when the possible future failure modes are low-risk: e.g. benchmarking isn't even part of what one would ship to production and the worst case for likely() and unlikely() is to make them no-ops if incompatible with future alternative.
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.