I am surprised by how many people are fooled by that, admittedly well written, but light on technical understanding, post. Retelling anecdotes is all it is. Apparently "asm.js" is bad because some developer doesn't like it. Apparently garbage collection needs five times the amount of memory. And also pixel buffers for images (which do not need to be scanned by a collector) slow down memory management. And lastly, you need highly optimized native code running on an I7 in order to handle GUI events.
It *seems like* the post is full of hard data and facts, but it isn't really. How much performance is needed by a typical GUI app given that it doesn't occupy 100% CPU? Not answered.
Can't the CPU intensive parts be done in "asm.js"? Not answered.
Finally, isn't the success of Android (and the existence of WP8) hard proof that a garbage collected languages are usable on mobile devices? Not answered.
I am sure most people will think I am trolling, since they are simply looking for validation of their existing opinions, but if we looked at the problems objectively (and there are real problems), perhaps we could really begin to address them.