I find it hard to take this article seriously when it's about issues with a framework: * that was still in beta/upgrading to the official version that was rele

I find it hard to take this article seriously when it's about issues with a framework: * that was still in beta/upgrading to the official version that was released last week * that was redesigned from the ground up by a company that is pretty intent on not doing things in JavaScript (see Dart, TypeScript docs but no ES5 docs) * whose original announcement of versional incompatibility was one of the major reasons its competition became popular * has clearly been attempting to frankenstein a lot of ideas from other libraries/frameworks in awkward ways The JavaScript community definitely has warts - I have zero issue with that statement. But the real problem comes from developers from other language-communities making blanket statements about the JS community while using tools that are clearly marked as unstable when they could've just as easily (actually... much more easily) written said app with any library/framework that wasn't released literally a week ago or even used raw JS - an API that hasn't had many breaking changes or compatibility issues in quite a while.