Server-sent events, WebSockets, and HTTP

Re:Server-sent events, WebSockets, and HTTP by treve on Sunday February 20, 2022 @01:53AM (#30403778)

I knew what this was going to be before I clicked it. This gets posted way too often any time a new thing is proposed. If the sentiment were universally true, we'd get very few new standards.

New ideas get proposed all the time, many of them fail and some are successful. We are better off for that. Don't discourage people from participating in the marketplace of new ideas. It's snarky and not constructive.

[ Parent | on HN ]

Re:Server-sent events, WebSockets, and HTTP by EGreg on Sunday February 20, 2022 @02:11AM (#30403863)

Actually I was summarizing his article. The situation he describes in pubsub for Websockets is exactly this.

[ Parent | on HN ]

Re:Server-sent events, WebSockets, and HTTP by josephg on Sunday February 20, 2022 @02:56AM (#30404050)

Thats not a summary, any more than "action movie" is a summary of Iron Man.

That comic cleverly names a common technical motivation. But it doesn't summarize the work because it removes all the interesting & relevant technical details.

Its also really done at this point. That link has been posted 733 times in HN comments[1]. It was funny the first time, but its time to let it die.

[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

[ Parent | on HN ]

Re:Server-sent events, WebSockets, and HTTP by treve on Sunday February 20, 2022 @02:46AM (#30404000)

The way you wrote this sounds like you disagree with my sentiment because I misunderstood your original intent with linking the xkcd, but I understood that you felt that the comic was an apt description.

[ Parent | on HN ]