Please log in or register to post a reply.
Seems to mostly complain about type safety, which I agree with. The cloning position thing, it seems like wouldn’t be very hard to work around and passing by reference is kind of a necessity.
The three major issues he posted are indeed a problem, although they are just inconveniences. I’ve learned to accept that for the greater good that browsers at least offer the ability to become gaming platforms and even much more. Plus you get use to the limitations rather quickly and just work with it. ECMAScript 7.0 has plans to evolve the language from out of the stone age. Overloading, concurrency, real classes.
I guess Google chrome can read asm.js now. I can run Epic Citadel at 43 frames per second, 1600 x 900 on my amd laptop with an A8.