59 karma · joined November 7, 2013
Each time the probability drops below 40% (in your example) it is likely because the fair odds swung in the latest polls. To attempt to take advantage of this is to ignore the recent evidence (conditional upon that evidence being quite different to the current concensus).
It's not at all unreasonable to do so, but isn't arbitrage. What if all polls started being increasingly conclusive leading up to election? 40, 39, ..., 0. No surprises and no arbitrage.
Perhaps another way to express this critique of Silver's methodology is that it lends too much weight on recent outlier observations? Sure if you knew this you could profit off these swings, but making the arbitrage argument doesn't add much to the discussion to my mind.
However a rational (impartial?) actor should be willing to take that risk if the premium is big enough. That could mean buying pre-fork or selling pre-fork if there is an obvious opportunity. Which means in an efficient market the risk premium should be zero "on average". It's hard to reason about averages with one sample but that sample was distinctly not zero!
Since I personally don't worry about centralisation and "trust", I like the idea that a system like the blockchain could be used to revolutionise payments without the need for tin foil hats and proof-of-work.
I think in the scheme of things, no matter how bad things get the planet won't even notice us. However the question remains what life will be left to see it when it does finally return to normal.
Ridiculous as it might sound, that implies it would actually take less work to devise a path for Python2 that's backwards compatible but still has a future, and invest the time to backport all 3-only code, than it would to proceed with killing off 2 and porting everything over. It's also nothing more than everyone whose code is 2-only is being asked to do sometime in the future (they chose "the wrong competing standard" and have to pay the cost). Either way someone has to foot the bill for a unified Python but couldn't it just be that the early adopters of 3 could pay that cost if it saves updating (say) twice as much legacy code in favour of backporting the 3-only code?
Of course, the future version of Python should be the best form of the language with the right features, and that's why it was decided to kill off 2, but if after this many years the initiative hasn't completely succeeded, there's always the option to reverse course.
Heck, in the time until Python 2 is officially gone, maybe this new fork will evolve into a better language than 3 and still be backwards-compatible with 2!
For now I'm sticking with 2.7 for as long as I can but will just accept it when the time comes.
[1]: https://mobile.twitter.com/vlasovskikh/status/80172061331236... for example (I don't think I've made a controversial claim here but could be wrong)