Hacker News Reader

Comment by andros | Hacker News Reader

The soap opera continues here: https://en.andros.dev/blog/bd74e61a/were-fighting-over-the-w...

Would really love to read this in your own words. In any case, I find the rationale for each of your points to actually better support the SSE approach. Your post actually sold me more on why I should not use websockets. Interesting.

I'm very happy to know that I've made you think, and that you've wisely chosen SSE for absolutely all cases. That's what a senior professional often does: limit themselves to one technology.

Less is more.

Who is talking about limiting to one technology?

I'm saying websockets are not fit to purpose and I can't see a compelling reason to ever reach for that particular technology any more than I'd reach for COBOL. Sadly, the browser environment gives us very few choices for streaming data connections.

Really though, I suppose I am limiting to a single technology: HTTP. Which kind of makes sense, I am putting hypertext content in a hypertext client over the hypertext transport protocol. If browsers spoke SSH, maybe I'd use that instead. I can't see a use case where adding a second protocol to my apps justifies the large increase in complexity when the capabilities are already better provided by the protocol that I'm already using.

As a fellow senior professional I too keep vacuum tubes in my toolbox.

Now I'm convinced on HTML over WebSockets!

Love the nuance that is going on. Absolute blast to read posts by people that truly understand the technogy they are working with.

I'm learning a lot. Technology is full of nuances and details.

Everything old is new again: "The SSE mechanism was first specified by Ian Hickson as part of the "WHATWG Web Applications 1.0" proposal starting in 2004.[3] In September 2006, the Opera web browser implemented the experimental technology in a feature called "Server-Sent Events""

Rob McCool is rolling in his...house. https://www.rfc-editor.org/info/rfc3875/

ai slop

I wish! It would have saved so many hours and drafts….

> The number is real. But there's a catch.

> The gap vanishes. It isn't measuring WebSocket against SSE, it's measuring

> And here is the deeper part the reply misses:

> In short, it isn't a structural problem, it's a design one.

> The real argument isn't the wire, it's the architecture

> Where SSE genuinely wins

> What really separates the two models is the architecture

Yep all very clearly AI writing.

> drk points out that the SSE stream is one-way but your app isn't

oops

I don't know why you think you can lie about this.

https://www.pangram.com/history/3e369754-75da-4922-8386-c0f3...

(Cue pivot to "oh, I only meant that it wasn't slop, I never pretended that I wrote a single word of it.")

Hm, Andros I do have my doubts - I know that you are a proponent of generative AI. We had a discussion over your outspoken opposition to https://human-emacs.org/.

I also know that you are an excellent writer/thinker, even prior to the advent of generative AI.

I'm in two minds here, and don't want to insinuate that you are outright lying, but I do believe your workflow relies on generative AI.

There is value in disclosing how you use generative AI to help you write articles. See https://www.bydamo.la/p/ai-manifesto or https://sive.rs/ai.

If you do use generative AI, may I suggest that you review the choice of licence: https://creativecommons.org/licenses/by-nc-nd/4.0/

> NoDerivatives — If you remix, transform, or build upon the material, you may not distribute the modified material.

If you do use generative AI, it feels hypocritical to use this licence while using a technology that essentially tries to circumvent the copyright issue by remixing, transforming and building upon the material it has ingested.

It's so, so clearly written by Claude. What are you talking about. Do you really think that you can fool people with so little effort?

Reply on news.ycombinator.com