new | show | ask | jobs Github

nchmy 5 hours ago

A good response to this post

https://yagni.club/3mstlyuxe5s26

▲

andros 3 hours ago | parent | next [-]

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

▲

tommica 2 hours ago | parent | next [-]

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

	▲	andros 2 hours ago \| parent [-]
		I'm learning a lot. Technology is full of nuances and details.

▲

wild_egg 2 hours ago | parent | prev | next [-]

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.

▲

andros 2 hours ago | parent [-]

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.

	▲	Kinrany 18 minutes ago \| parent \| next [-]
		As a fellow senior professional I too keep vacuum tubes in my toolbox.
	▲	wild_egg 2 hours ago \| parent \| prev \| next [-]
		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.
	▲	throw1234567891 2 hours ago \| parent \| prev [-]
		Less is more.