W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 12 Feb 2015 13:55:28 +1100
Message-ID: <CAAWBYDAGM0jkEeQbROzx+Dy-MUvTTe-jA_Tx6aFE2Kkcwp4qSg@mail.gmail.com>
To: Marc Fawzi <marc.fawzi@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, public-webapps <public-webapps@w3.org>
On Thu, Feb 12, 2015 at 1:45 PM, Marc Fawzi <marc.fawzi@gmail.com> wrote:
> this "backward compatibility" stuff is making me think that the web is built
> upon the axiom that we will never start over and we must keep piling up new
> features and principles on top of the old ones


> this has worked so far, miraculously and not without overhead, but I can
> only assume that it's at the cost of growing complexity in the browser
> codebase. I'm sure you have to manage a ton of code that has to do with old
> features and old ideas...
> how long can this be sustained? forever? what is the point in time where the
> business of retaining backward compatibility becomes a huge nightmare?

When someone comes up with something sufficiently better to be worth
abandoning trillions of existing pages for (or duplicating the "read
trillions of old pages" engine alongside the new one).

Received on Thursday, 12 February 2015 02:56:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:43 UTC