Funny enough, just yesterday I did a spike into introducing one of the mentioned frameworks (SolidJS) into a no-framework legacy app, and I’m almost certain it’

Funny enough, just yesterday I did a spike into introducing one of the mentioned frameworks (SolidJS) into a no-framework legacy app, and I’m almost certain it’s the right move. The app is over a decade old, with a variety of different approaches and the tangled data flow that you’d probably expect of that… despite effectively having evolved an informal framework internally. Solid is a perfect fit for a couple reasons: 1. Its “components” compile away to plain DOM operations, so it’s well suited for a gradual transition story: existing behavior can wrap and be wrapped by new/replacement components without a need to reconcile between them. 2. Its reactive state model fits the app’s requirements very well, particularly in terms of needing to maintain two related but quite different representations of the data in tandem. Solid’s performance being about as near to vanilla JS as possible is just bonus points to me, but certainly will ease concerns on my team.