News for hackers. Stuff that matters.
Re:HTTP 2.0: GTFO (General Termination of Future Operations) by bsdetector on Monday January 27, 2014 @08:21AM (#7130146)
GTFO and ENHANCE_YOUR_CALM are symptoms of an unprofessional design process. It's not bad that a core standard be plain and functional, in fact it's a sign that the people designing it did so with the seriousness it deserves.

If the http wg actually listened to PHK there would be some hope for it not to end up with the complicated garbage that it is now, but they don't.

Re:HTTP 2.0: GTFO (General Termination of Future Operations) by TeMPOraL on Monday January 27, 2014 @09:25AM (#7130382)
> GTFO and ENHANCE_YOUR_CALM are symptoms of an unprofessional design process.

I'd chose "having sense of humour" over "professional" every day.

> it's a sign that the people designing it did so with the seriousness it deserves.

Or it's a sign that the people designing it are too serious, focusing on political correctness and not on doing good engineering. Creativity, care about the product and sense of humour often go together.

Re:HTTP 2.0: GTFO (General Termination of Future Operations) by Karunamon on Monday January 27, 2014 @10:26AM (#7130741)
Give me humanity and a sense of humor over PC-"professionalism" any day of the week and twice on Sunday.
Re:HTTP 2.0: GTFO (General Termination of Future Operations) by teacup50 on Monday January 27, 2014 @03:51PM (#7133133)
This kind of "sense of humor" doesn't belong in a formal specification document. Sorry.
Re:HTTP 2.0: GTFO (General Termination of Future Operations) by rakoo on Tuesday January 28, 2014 @03:17AM (#7135994)
But why ? The point of a specification is that everyone agrees on how we talk together, it's not about Being Professional and Looking Serious.