You could work for 50 years and never need those… it just depends on what you’re creating / how many devs and so on.
I know some guys who over the years wrote their own framework. It works great… for them.
I know some guys who over the years wrote their own framework. It works great… for them.
It’s always like: you have dozens of interactive controls in this view, it’s getting out of hand, you should use this language that compiles to HTML and JavaScript and carry all these dependencies. To which I always reply: no thanks, I rather deal with the dozens of controls.
I think that’s a given for any proposed standard. We all get a common way we understand things and can even just communicate about a thing.
The solution they sell is technical, like state management, reusable components, etc. Which I don’t find convincing.
And that's fine, these tools don't solve what you search for.
A dozens of controls multiply with a dozens of events are already a quite big amount of points of failure, so people gladly trade it with the dependencies (what's the issues with dependencies anyway?).
So yeah, not many people want to be good, and only hire good people like you to use the hand tools and "just do it correctly". Most acknowledge their downsides and use proper tools to aide them.