EmployeeNumber8

You missed the "this" keyword when you assign to leftPressed and rightPressed I'm going to assume it was just a typo. We've all done it haha.

Chris made a good observation, so I've modified the code snippet. However, there is absolutely nothing "wrong" about using uppercase.

To make it a bit more "object oriented", you could revise it such that the internals of Rectangle are private. I'm sure you'll find several ways to achieve this. Here is a one way. var CreateRectangle = function(left, top, right, bottom){ //private state var width = right - left; var height = bottom - top; var getArea = function () { return width * height; } return { getArea: getArea };}

Haha very cool. Good work man!

Ok cool. Thanks.

Is there a way to submit tutorials/articles in here? Lots of smart guys here... it would be cool if we could create tutorials for newcomers. Something similar to the articles section on the gamedev.net forums.

Are you using Chrome on Windows? Try locking your computer (windows key + "L") during the audio and see if the sound stops. It happened to me once but I forgot to submit it as a bug.

+1 for Webstorm +1 for Sublime Text I'm on the same setup as Chris.

The way it is written in the MDN documentation makes sense. If you maintain a reference to the oldChild with var, then it will persist in memory. The spec doesn't seem to specify what user agents should do here regarding memory. I would assume that is beyond the scope of the spec. This is directly from MDN:

It will get garbage collected if there are no references to it. I remember confirming this last year in Chrome, Firefox, Opera and IE8+ Just be mindful the this open bug for Chrome regarding memory leaks. If you see memory usage go through the roof, then it may be the bug... and not the fact that you adding/removing many DOM elements. Hopefully they fix it soon - very annoying!

Very cool!

Define "harder to scale". I've found it quite easy to scale. When you talk about what the language was designed for, and the async model - those arguments are purely academic... but in the real world, companies like eBay, 37signals, Cloud9, Yahoo!, LinkedIn, Flickr, Microsoft , Twitter (on a small scale), Instagram (I think)... are all using nodejs on the server side. These are companies that really have to deal with massive scaling. By your own admission, you've only "tried" it. Show some real world examples of how/why nodejs is a poor choice for scaling. Projects, applications, companies using nodejs

Very cool. I will definitely be using this.

@BlueMagic You should post a separate topic in the Audio forum for Howlerjs

I'll support any obsolete browser, but it will cost the client more.