I get your frustration: only being partially invested in front-end web dev, the constant churn of what people consider viable stacks, techniques and architectur

I get your frustration: only being partially invested in front-end web dev, the constant churn of what people consider viable stacks, techniques and architectures can be maddening. It can all seem like a race to implement the hottest javascript du jour in some finicky framework or library while sweeping inscrutable, increasingly complex webpack implementation details under the rug... until they pop out, or the rug catches on fire, or the floor gives out, or any other inevitable thing happens that precludes ignoring them. Maybe plastering a power strip into a wall rather than doing proper electrical work is a better metaphor. Everybody knows it’s a bad idea, but someone made a thing that automatically provisions and deploys new strips, and someone made a thing that plugs stuff in, and someone made a thing that mixes and applies plaster which was replaced by a drywall thing but we still call it plaster, and someone else made a thing that does it in 10 rooms at once… That said, this seems like a bigger step towards simplifying both the development process AND the toolchain. It only works in newer browsers so it doesn't immediately work for all use cases, but it's good enough for some. We're quickly approaching the point where browser-native implementations of more recent, better designed scripting features are widespread enough to rely on. That should both simplify and stabilize front-end web development for quite some time.