But I can't really get behind the author's stance that it is wrong for people to have preferences (even strong ones) about which javascript frameworks they like to use.
Exactly. As a developer, I can appreciate that every framework has different strengths and that you should use the tool appropriate for the task, but the fact of the matter is that I have work that needs to get done now and if I spend all my time choosing the perfect tool, I won't ship anything. I have a toolbelt stocked with the tools I like best. I wouldn't want to stifle the discussions on which one's "best," though, because they can be really informative for those looking to add a new tool to their stack.
Exactly. As a developer, I can appreciate that every framework has different strengths and that you should use the tool appropriate for the task, but the fact of the matter is that I have work that needs to get done now and if I spend all my time choosing the perfect tool, I won't ship anything. I have a toolbelt stocked with the tools I like best. I wouldn't want to stifle the discussions on which one's "best," though, because they can be really informative for those looking to add a new tool to their stack.