Fads are tempered by a community of people anchored in a deep understanding of the technology. As talented as many FE engineers are, I can count on one hand the number that I've met that have a deep understanding of things like await/async + Futures, closures, DOM trees, etc. These things are (perhaps unfortunately) required to do FE work, yet the engineers using them don't fully understand them, so they don't know how to discern if helper libraries are actually helpful.

Additionally, I'd argue FE draws more junior people in general, because of the theoretical rapid feedback loop, and the fact that you can "make something that looks cool" with relatively little effort (relative to a BE engineer). These junior people add confusion to the chaos of the community because they don't know what they don't know, so they're cocksure about their opinions. And as long as they've "made something that looks cool", even if the architecture behind it is hot garbage, it buys them cred in the community.

Somewhat related, I've been using Flutter for a recent FE project and I'm in love with it. It's more for webs/mobile applications than websites, but the ergonomics of it feel like a coherent vision. The people maintaining it (Googlers) are excellent, and the Dart library community seems to know what they're doing. Furthermore, the FE design choices are based on Material Design[0], which is backed by (some informal) research by UI and UX professionals, so you don't have to sweat usability quite as much as you would starting from scratch.

0. https://material.io/components?platform=flutter