Worse the article makes the developer mistake of briefly arguing for React comparative to Vue and Angular as opposed to why bother with the giant monolithic fra

Worse the article makes the developer mistake of briefly arguing for React comparative to Vue and Angular as opposed to why bother with the giant monolithic framework in the first place. This is problematic in that it assumes a level of knowledge upon the reader that is contrary to the point of the article in the first place. This is a common uninformed hiring mistake that implicitly assumes there must be a giant monolithic framework. It suggests you don’t really know what you want but that you think you need it because it’s popular. There is a silent immaturity in this kind of reasoning. Does that ease hiring? I suspect it does. Any time you can slap an agreed upon term to an abstract concept the concept becomes something that can be communicated past. Just because candidate availability increases does not suggest candidate performance or fitness for work is any different. That is the elephant in the room for these kinds of subjects as the result is over paying for unqualified talent.