I have exactly the same experience. Very pleasant to write programs that are going to be used by more than 10k users at once.

Indeed, but not quite. Ask yourself if it was my intent to counter the person's claims by attacking the person. No, that was not my intent. I never intended to counter the person's claims. I was explicitly calling the person out based on tone and style of his/her comment and others in his/her comment history.

The thought even crossed my mind while carefully drafting the above comment that I ought to preempt the accusation that I was committing this logical fallacy but I decided not to and now I wish the opposite.

Anyway, I hope you see the difference?

Pro-tip: People are going to have strong opinions here. Rebutting their message rather than the delivery ends up rebutting both.

This is not an Ad Hominem at all..

I'm from Estonia and I've never heard about the flatiron-coffee-thing. Wtf is it.

I had the same experience. socket.io was too flaky. Also I didn't need Flash support etc. In the end when I started to fix socket.io code to suit my needs and to handle the weird errors, I simply hacked together something in Go that pulls messages from Redis and writes them to Websocket or as HTTP GET response. It has only Websocket and HTTP POST/GET support but who cares. The simpler the code for handling these things, the better. Maybe socket.io got too complicated or something.

In my experience, Websocket is not something to depend on. But it's really nice to have and should be used as an upgrade if available.