...for instance, if JavaScript is "a potential threat to...Java" - uhm, which came first? There is also very little "new" technology in .NET. It is a new focus for MS platforms, but from my POV it is mainly wrapping a class system around a bunch of methods that have been used successfully in the past by those who dug around a little.
To me, the real difference is: giant, monolithic, monotechology application development within a vendor's framework vs. structured layers of elegant, simple components built using mostly open standards. XML technologies - in their native
incarnation, not all wrapped up in a language's class hierarchy - give a level of transparency, reuse and light weight to an application that is unattainable with the former method.
And while it may be "...really, really, really hard to build something like Google Maps", with their preloading of tiled images, etc., I was using client-side JavaScript objects and XMLHttpRequests through hidden frames over three years ago to fetch and repaint only those page components that needed to be changed. I'm sure there are other developers who were, too. It's not rocket surgery.
I keep saying to those who will listen: "It's not the technology being used that's crucial. It's the people using it and whether they fully exploit its capabilities."