Comments for Stephen Belanger

Comment on You are not lean, stop pretending. by Stephen Belanger

Stephen Belanger — Tue, 17 Jan 2012 17:56:00 +0000

It’s the curse of over-funded startups. Their impatience leads them to throw manpower at every “problem” they encounter, even if it’s just a minor delay. They don’t seem to get that, just like the system they are building; the more points of required communication between entities, the greater the latency will be per request.

Adding a new person to a project slows everyone else down almost as much cumulatively as that person adds value.

Comment on A simple explanation of “new” in Javascript. by Jon H

Jon H — Tue, 17 Jan 2012 13:36:00 +0000

See this:
http://stackoverflow.com/questions/2449254/what-is-the-instanceof-operator-in-javascript/2449264#2449264

Comment on You are not lean, stop pretending. by Jon H

Jon H — Tue, 17 Jan 2012 13:32:00 +0000

Heck of a post…I agree 100%. I’ve seen large branded companies with 100s of developers and designers with horrible products. It doesn’t matter how much money or resources you have. If you don’t get it right with 1 person how are you ever going to get it right with 100s.

Comment on How to make Socket.IO work behind nginx (mostly) by Stephen Belanger

Stephen Belanger — Wed, 14 Dec 2011 17:52:00 +0000

It goes wherever your Socket.IO code is defined. I like to put it right after io.attach().

Comment on How to make Socket.IO work behind nginx (mostly) by hosam.ebrahim

hosam.ebrahim — Wed, 14 Dec 2011 14:12:00 +0000

Can anyone please tell me exactly the file name I should update it, I don’t know where to override this function?

Comment on The Infinite Genies Paradox by picko

picko — Wed, 07 Dec 2011 04:50:00 +0000

The disney’s genie is a little different from some of the other genies. Unlike the genie from aladdin, most genies seem to be tricky. From what I remember when you wish a genie free, in exchange of that genie you are trapped and become a genie to take his/her place.(Or if the genie said a genie can only grant you three wishes would mean that it didn’t matter which genie you asked the wish for. Kind of like an ATM machine where it doesn’t matter which ATM you go to, you would still have the same amount of money) Also wishes can be interpreted differently, like I wish I had trillion dollars and the genie would give you trillion dollars worth of coin which crushes on top of you. As for the wishing the third wish to not be granted. The genie could simply vanish your existence from the beginning. By doing so, your wish would come true because you would have never wished for the wish and so there is no wish to come true. At the same time your wish didn’t come true because although you never wished it the wish was granted. So it’s kind of answering a paradox with a paradox. haha

Comment on How to make Socket.IO work behind nginx (mostly) by Stephen Belanger

Stephen Belanger — Sat, 03 Dec 2011 09:00:00 +0000

Most of the “auto-scaling” cloud host type services can’t give unique IPs though. Typically they are just a thin layer on top of AWS.

Comment on How to make Socket.IO work behind nginx (mostly) by Srirangan

Srirangan — Sat, 03 Dec 2011 08:58:00 +0000

Umm .. it should work for vhosts if they have a dedicate IP. The problem was the clash of ports if both the tcp {} and http {} blocks were declared for all IPs.

Comment on How to make Socket.IO work behind nginx (mostly) by Stephen Belanger

Stephen Belanger — Sat, 03 Dec 2011 08:57:00 +0000

Yep, I’ve seen that fix too. Unfortunately, it doesn’t work for vhosts. So cloud hosting services like dotcloud can’t use that.

Comment on How to make Socket.IO work behind nginx (mostly) by Srirangan

Srirangan — Sat, 03 Dec 2011 08:54:00 +0000

Hmm.. the way I got Socket.io to work with Nginx at Review19 – http://review19.com – was to compile Nginx with the TCP Proxy module (https://github.com/yaoweibin/nginx_tcp_proxy_module). Didn’t require any modifications of the Socket.io code but I needed to declare an additional tcp {} block in nginx.conf