Maybe the platform runtime one, but I could be wrong. ;)

Node haha? Dang. As mentioned in an answer to another comment, perhaps framework was the wrong terminology to use, and something more all-encompassing to reflect what is wanted would've been better.

What do you think a developer using Javascript should use/know right now?

Also, is React a framework?

What would you say is the best way to describe React?

Hard to say.

"A JavaScript library for building user interfaces" is what React calls itself.

Hi Jonaldomo - could you clarify what you mean?

He is saying that Node is not a JavaScript framework. It is technically a back end scripting language. So maybe you would do well with a better umbrella term like skills or tools.

Noted – use of terminology could've been more accurate, but for the purpose of this article we tried to keep it quite simplified. Perhaps the wrong approach with regards to accuracy.

What were your thoughts on the broader points of the post?

I agree with it in terms of generally desired skill sets. Angular rose to prominence very quickly and Node has had a very steady grassroots climb. Backbone has been on the decline for a while now. I don't think React has the klout to really become a commonplace skill. We will see what happens with Angular after 2.0 though.

What do you think will happen with Angular after 2.0?

Either demand will explode again, or there won't be much new adoption outside of proof of concept projects. They basically will be losing much of the continuity other frameworks have.

I personally/professionally will consider using CanJs and EmberJs from now on.