> It's "declarative" right up until you're debugging stateful hooks, or resorting to useRef, or trying to reason about when a "component" re-renders
Maybe they should have modularized the core library more and have these things be separate, because the core idea of a uniflow pattern with reactivity is good.
I think what happened, at least in frontend, is that the industry pushed away from having engineers do any design or architecting on the frontend. All of these high level patterns have been "outsourced" to frameworks, and the result usually is something that has trouble scaling and adjusting to whatever domain it's in.
That's what SolidJS does. IE the signal implementation is completely stand alone. I feel like it's better at doing what react purports to do then react is.
* think what happened, at least in frontend, is that the industry pushed away from having engineers do any design or architecting on the frontend. All of these high level patterns have been "outsourced" to frameworks*
I don't think react patterns are particularly high level, or do they save you from architecture. Whether it's vanilla JS or react, you still have to design.
In my experience it requires a longer learning curve for the various frameworks than to simply learn the relevant Web API. My learning is very much JIT and over time I have built up a robust class library that gets my stuff done. When I get stuck ChatGPT suggests fixes that sometimes work and spare me from losing more hair.
copypaper•1y ago
LAC-Tech•1y ago
I think that's why I wrote this - I almost completely fail to see them.