2) That said, Javascript isn't going away. We will all be managing thousands of lines of Javascript because… that's where applications are going - client side. Good luck convincing all the browser vendors to swap.
Anyhow, I know you're just trolling but you have to up your troll game - 98% of apps fall in between "toy demo" and "twitter".
Like, that you've actually experienced and said "You know, I'm not saying this just because I'm not used to it. This bit right here is a design flaw".
This is such a tired and boring argument by this point, but I'm willing to entertain it because duck typing is at the bottom of my list of worries.
I don't think you really believe a web development framework and a feature rich blogging product were actual competitors but are simply creating strawmen to support your view. Drop the crap.
The Rails use case was always truly limited. I still don't know any application that achieved maturity and stayed coded in Rails. For a while that was Twitter, but then they started moving stuff over the jvm.
Node will probably end up in a similar way, because at the end of the day no one wants to manage thousands of lines of Javascript (or any other language that doesn't enjoy the benefits of a statically typed ide).