Live data from Hacker News

HTTP 2.0: GTFO (General Termination of Future Operations)

http2.github.io

Post reply on HN

Print view View original

1–10 of 89 posts

HTTP 2.0: GTFO (General Termination of Future Operations)

#1

Post by ryanf » Mon, Jan 27, 2014, 2:15 AM UTC

HTTP 2.0: GTFO (General Termination of Future Operations)
http2.github.io

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#2

Post by vsviridov » Mon, Jan 27, 2014, 4:24 AM UTC

Needs TITS verb now to complete the picture.

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#3

Post by returnint » Mon, Jan 27, 2014, 4:28 AM UTC

what does GTFO stand for?

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#4

Post by [deleted] » Mon, Jan 27, 2014, 4:34 AM UTC

vsviridov wrote: post #2

Needs TITS verb now to complete the picture.

[deleted]

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#5

Post by sdegutis » Mon, Jan 27, 2014, 4:35 AM UTC

This play on words is a pretty okay joke.

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#6

Post by kul_ » Mon, Jan 27, 2014, 4:45 AM UTC

returnint wrote: post #3

what does GTFO stand for?

get the fk out!

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#7

Post by RyanZAG » Mon, Jan 27, 2014, 5:45 AM UTC

The complexity difference between HTTP1 and HTTP2 is pretty huge. Not sure if they're even remotely the same protocol anymore.

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#8

Post by kevinchen » Mon, Jan 27, 2014, 5:48 AM UTC

kul_ wrote: post #6

returnint wrote: post #3

what does GTFO stand for?

get the f k out!

No, it stands for "General Termination of Future Operations."

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#9

Post by knieveltech » Mon, Jan 27, 2014, 6:03 AM UTC

vsviridov wrote: post #2

Needs TITS verb now to complete the picture.

You code in Ruby don't you.

Re: HTTP 2.0: GTFO (General Termination of Future Operations)

#10

Post by bitwize » Mon, Jan 27, 2014, 6:03 AM UTC

RyanZAG wrote: post #7

The complexity difference between HTTP1 and HTTP2 is pretty huge. Not sure if they're even remotely the same protocol anymore.

The old Unix model (simple, do one thing, text formats, etc.) is dead. The world has come to prefer code and protocols which perform well at scale.

Post reply on HN