I find your article a bit incoherent. On one point you seem to use the old “engineers” argument that one should choose the right tool for the Job. Which is and always was kind of a “Captain Obvious” position. On the other side you seem to discourage people to write openly about their experiences with those tools; which may be biased, but also can contain valuable information about how and why to choose something for a task.

Beside of that — the Tool analogy in “Right Tool for the Job” is not very useful most of the time. Choosing between Frameworks like React or Angular often is not a decision between a hammer and a spanner; it often is a decision between a “Mannesmann” or a “Proxxon” spanner. The decision is then not to use the “right” tool but more like the “available” tool. It is not a good idea to bring in Angular into a React Project or vice versa. Shared experience with tools can help though to make clear, that a particular “brand” of tool may break under certain forces/constraints. Like Angular 1 in certain contexts of big DOMs and many active bindings.

I strongly disagree that people should be demotivated to write about their experiences with JavaScript Frameworks. Even if their experience is fresh or their bias big — it just doesn’t feel right to solve the “information selection” problem from this side. Maybe those who feel affected like you on such topics should just stop reading those articles?

;-)

Developer — Author — Photographer — Guitarist

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store