Well, not so much "some length", but they introduce the distinction and make that clarification briefly towards the end of the post. But they don't go into detail about what the distinction really is. Some of the projects I've used React for have been consumer-facing, informational "websites", but have benefited from the structure and data integration that React enables.
Anyway, is there really such a widespread pattern of employers requiring React experience when plain-vanilla HTML/JS/CSS is all that's needed on the job?
The weight of the post rests on that assumption, but where's the evidence for it?
Anecdotal, but a lot of front-end positions I see do require either of a) experience with some framework or b) experience with React specifically.
But I agree with everything you’ve said in both your comments. I think that a lot of companies are asking for React because a lot of them are building web apps or “mildly interactive” websites, where (I agree with you) React is also fit for purpose.
Anyway, is there really such a widespread pattern of employers requiring React experience when plain-vanilla HTML/JS/CSS is all that's needed on the job?
The weight of the post rests on that assumption, but where's the evidence for it?