It’s understandable why there is no cohesion in the JS community. At the end of the day, when you have an open source driven community with a LOT of devs it’s bound to be a lot of churn for the reason that there is no one company that is driving the direction on where dev effort should be be focused.

The unfortunate thing about that is obviously we have day to day devs that need to solve real world business problems using frameworks and libraries built by people that are just constantly evolving proof of concepts LOL. Unlike mobile that is more focused on building consumer facing apps, the JS community is basically a hotbed of experimentation which is only bad when devs need to deliver value for a business. Otherwise it’s great for validating techniques that the dev community wants to coalesce around. We could argue that React validated building declarative UIs (even though it was around before React). But because of the JS community us mobile devs got Jetpack Compose and SwiftUI.

For this reason, I appreciate the JS community but I want nothing to do with it. In my eyes, it’s just there as an R&D community that will have ideas spill out in to other communities that are more cohesive.

As devs, I think one thing that we have to accept is that we got in to this to BUILD stuff. It’s the build process that drives a lot of us to create. You will often see people on GitHub ask the author of a lib/framework “Why did you create this instead of extend library/framework X?” And the answer to that question, is why be a dev if all you do is cobble together other peoples work? LOL

This articule summarizes everything I’ve been saying about that ecosystem and tools for years, and been called a “hater” for that.

Not primarily a front-end dev, I also feel that the ecosystem and tools are sometimes confusing/overwhelming