I think the point of the article, which was rather subtle actually, is that "top of their game" is best defined in more general terms than simply "skilled in the top random webby crap from from the last 18 months".
I've been able to rewrite front-end code in a different framework with less than 1/5th of the code to maintain.
And about 10,000x as many dependencies, not to mention (if not exactly a shit-ton) a considerable degree of implied bulk in the form of new abstractions ("transpiling") and random contextual crap (packaging, etc) to maintain as well. And the implied path-dependence (for the sake of temporary benefit that comes from adding X, Y and Z to the project... it's going to be that much harder to refactor and shift to something else). All for the sake of a simple autocomplete form, and maybe a popup or two.
Which is exactly what's so cool about "boring" developers -- they see not just the positive tradeoffs in using the shiny stuff ("1/5 as much code") but the negative tradeoffs ("So you mean that hot new AngularJS thing everyone was yelping about 3 years ago... suddenly isn't looking so hot anymore? How come?") as well.