Nice article, thnx!

Even though I personally don't like Web Components – I mostly work with enterprise code where communication and integration between components is complex enough to get the benefits of Web Components and the overhead of managing Web Components will be very visible, in the last years I'm inclined to Reactive Store-based solutions.

When you have a data layer, a more or less complex service layer, and a view UI associated with the relevant part of the store(s). And this approach tends to be more or less framework independent and flexible enough to have, for example, microfrontends where the same reactive store is used by multiple UI engines: some from React, some from WebComponents, some Vanilla or Svelte... even Angular.

And as you say, balance is the key. Because you can have the speed and convenience of the development process (frameworks) or the flexibility and, emm, manoeuvrability for future (custom code), and this is very, very visible when you have to orchestrate manually all the glues between parts of the app.

Especially for long-lived applications.