>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/

The big issues for me are 4 and 6 - and the different styles of programming for classes / objects
that are use in different libraries/frameworks. Also:

http://www.alistapart.com/articles/getoutbindingsituations

Number 10 is a real doohh! Think of all the flak Python got for significant whitespace and
here an error is introduced even though curly braces are used... Stoooopid
But at least a nice argument for the style I prefer in C, Java and Javascript ;-)
Must think about how to formulate an arguement to train programmers eyes
to safe pattern in JS is better in Java as well as it sets a good mental base pattern...

>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.

Yes - that is the big windfall profit only few people seem to care about.
Afraid programming could be done without large drone groups ?

Silverlight HAD much of the same lure for me when it still was multi-platform targeted
(V2 on Symbian runtimes slow as hell, but working) - Dotnet in browser and backend possible.
MS as originator and closed source approach again showed the dangers of that approach,
although Xamarin seems to be currently on target on the mobile fronts selling devices.

>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".

IMHO this is the main lure of RoR: One fwk to rule them all...
Python plethora of backends cost them acceptance here.
Coupled with Python's relatively weak standing in mobile devices
(another GUI in Android, unwelcome in Apple land, WP7 ?) I really wonder
if we can avoid JS as default system script language in the middle term future.

I doubt the ability of Google to create a new Web(browser) standard:
why should Dart suceedd if the already running WebSQL (based on gears)
was scrubbed by an onholy alliance between MS and Oracle.
Or to put it another way: WebSQL tempts me more than Dart or native mode
to concentrate on Google based browsers, as that would open up the way
for client side persistance and/or caching in a useful way.

RIP Silverlight: My pet peeve of 2010...
RIP WebSQL: My pet peeve of 2011... (was earlier, but I realized the Oracle connection in 2011)

The reasons to pay MS for server side tools are getting smaller each year,
at least on the server linux is very alive, so an OS backend stack with either Python or Node.Js
for me is the target for xPhone and xPad apps, which can be read on the HW
used by the old folks as well - and I am horrified to realize that I am in the geezer group ;-)


regards

thomas