W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014


From: CIURANA EUGENE (pr3d4t0r) <pr3d4t0r.w3c@cime.net>
Date: Wed, 29 Jan 2014 08:25:40 -0800
To: <ietf-http-wg@w3.org>
Message-ID: <b32511490872fd8d21c21883e164d0e7@cime.net>

>> On Tue, Jan 28, 2014 at 1:22 PM, Adrian Cole
>> wrote:
>>> FWIW, when GTFO was
suggested last week at the working group, all people
>>> present had an
opportunity to dissent and I heard not a single dissent
>>> voiced!

>>> That said, I wouldn't conflate above PR/commit as a "popular move"
as who
>>> knows.. GOAWAY might actually lose a popular vote vs
>>> That said, silencing the argument is likely a popular
move, so maybe the
>>> description still fits.

I expressed this in the
GitHub comments about the issue, echoing it here as well because this
mailing list has a wider audience.

Use of GTFO is fine. Anyone arguing
that because foreign speakers may not understand potential slang is
being naïve or needs to get out more. I've managed development teams in
Moscow, Novosibirsk, Kiev, the San Francisco Bay Area, London, and
Japan. The use of slang or jargon derived from English in technical
documentation, implementations, code, or configuration has never
deterred anybody from applying the appropriate knowledge. GOAWAY vs.
GTFO -- if I were to implement a server or a client handler for this,
I'd go for GTFO as the most meaningful (and perhaps get a secret
chuckle, sure).

So -- can we keep this instead? Think of HTTP status
code 418 IMATEAPOT (which is Russian slang for "I don't know what I'm
doing"). Not many web servers or app servers implement it, granted, but
it's part of the official spec. And I've known teams in the US and
Europe who've used 418 as a placeholder for an app RESTful handler that
is only mocked up/yet to be implemented.

Just my $0,02.




http://eugeneciurana.com | http://ciurana.eu

Received on Wednesday, 29 January 2014 16:25:58 UTC

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