W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2014

Re: [whatwg] HTTP status code from JavaScript

From: Qebui Nehebkau <qebui.nehebkau+whatwg@gmail.com>
Date: Sun, 25 May 2014 18:16:40 +0100
Message-ID: <CAF_oMa1EOL9mmJw9zwKF7gVa_gt8mdNTOiQ1UG4vtMr2n8v+JA@mail.gmail.com>
To: Michael Heuberger <michael.heuberger@binarykitchen.com>
Cc: "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Tobie Langel <tobie.langel@gmail.com>
On Sun, May 25, 2014 at 8:34 AM, Michael Heuberger <
michael.heuberger@binarykitchen.com> wrote:

> Tell me a good reason why JavaScript should NOT have access to the
> status code?

There's always a good reason not to add new things. Call it inertia; every
new feature starts at -100 points. Something like this, which gives you
information you should already know and is only helpful when you've already
made some seriously questionable design decisions, probably shouldn't ever
overcome that initial deficit. Of course, that's just my opinion, but I
have a feeling I'm not the only one.
Received on Sunday, 25 May 2014 17:17:27 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:20 UTC