>http://net.tutsplus.com/tutorials/javascript-ajax/top-10-things-that-javascript-got-wrong/

This article is just a non-sense; any language has its rule and syntax - just like English, French, Russian, Chinese, etc.

> Maybe - but I bet it will be short lived

Good news, it's just the opposite.
Most frameWork (jQuery, underscore, Prototype, etc.) anticipate future ECMA specs and implement native functions whenever available; developer just has nothing to do (no version tweaking, no case, nothing), frameWork automatically adapts to browser's capabilities.

Javasript needs some learning (moderate for VFP devs), but it's rewarding.

thn

>OK I'll bite! Check out the list below. I have run into each one of the issue presented.
>
>http://net.tutsplus.com/tutorials/javascript-ajax/top-10-things-that-javascript-got-wrong/
>
>But the real truth is I hate having to program in multi-languages with different rules. Programming the server side is completely different than the client side. No wonder someone came up with node.js.
>
>And if you add in frameworks and maybe some other generators you can get a real mess. Just think about it - will it be that you (the programmer) will become "the jack of all trades and the master of none".
>
>Is it possible to build a framework that gets close to what VFP did - I think so. But at what cost! And in the end will you have the so call benefits of the web? Maybe - but I bet it will be short lived - because the web is changing way to fast and what you design today will old school tomorrow.
>
>Johnf