You're talking language syntax. Although it matters, it practically doesn't. People build stuff no matter what the language looks like. Look at Obj-C, that thing is horrid (syntax-wise) but look at all the developer adoption.
What is bad for innovation is to move back to the 90's where people had to handle local instances of applications, fix versioning problems, and have to install something just because they want one small piece of functionality.
This is a fallacy: in absence of a peek at some alternative world where something else was available, you can't tell that javascript improved or worsened the innovation rate.
Mostly interesting because of their content and what they do with it on the server.
> games
You've got to be kidding me. There is nothing technically interesting in any web game I've ever seen.
> social networking
Again, has nothing to do with interesting client-side technical challenges and everything to do with the content and community.
> You're talking language syntax.
Don't forget the semantics too.
You only hate JavaScript when you're starting out. When you get to know the language and how to use it properly, you begin to appreciate it in a very unique way. Until you understand what prototypical programming truly is, you don't understand JavaScript.
So you can understand and master JS (including prototypical programming) and still hate it.
I just wish they decoupled javascript engines and browsers, made a language agnostic api spec for the DOM, and just let html <script> tags require a language ref and the browser would be expected to try to find a runtime on the local machine or ask the user to install it. The monopolistic nature of javascript in client web browsing is bad for innovation.