Tue Jun 26 17:18:15 CDT 2012
On Tue, Jun 26, 2012 at 2:51 PM, Brian Granger <firstname.lastname@example.org> wrote:
> We are aware of these alternatives. My philosophy (and I think it is
> reflected in the rest of the team) is this: by sticking with plain
> old WebSockets, all we have to do is *wait* for the situation to
> improve. That is super easy to do! Once IE 10 comes out, we should
> cover most browsers. If we go another route, *we* have to do all the
> work, and in the end, we will throw that work away because WebSockets
> will eventually have universal support. That sounds like extremely
> low priority work to me.
+1 (and also with Min).
> People should not be running older browsers anyways. There is simply
> no reason, you almost have to try hard to run an older browser.
There are real-world scenarios where individual users are *forced* to
run older browser by constraints beyond their control, such as
university/school/company-run machines where they have no admin
control at all. So I do see that *in principle* it would indeed be
nice to support older browsers.
But given the extremely high cost of development to us of such
support, I just don't think it's a realistic proposition: we'd get
bogged in a tarpit of old browser support that would easily consume
all our limited dev resources.
So I simply accept that IPython isn't the right tool for those in such
constrained environments, unfortunately. We have to pick our battles
carefully if we're going to make progress, and this is one such
More information about the IPython-dev