3 ms·
Applaud the effort, and obviously I don't have the insight into the motivations behind the decisions, but I don't see this ending well. Why have multiple SPA f
by rco8786 9y ago
Applaud the effort, and obviously I don't have the insight into the motivations behind the decisions, but I don't see this ending well.
Why have multiple SPA frameworks on a single page? What happens when one fragment is built in React X.X and another in React Y.Y? It feels like you have to pull a bunch of different pieces together to form what would formerly be known as a "route" in more traditional webapps, and I'm not really seeing the upside here.
I hope we get a follow-up in 6-12 months about where this experiment goes.
- DasIch 9y agoNot sure about HelloFresh but at Zalando there are rules for that all fragments are supposed to follow so that this doesn't happen. In practice that means everyone has to use React in the same version, there is a shared library of components for grids, buttons to achieve consistency in look and feel and so on. You could have multiple SPAs in the same page but you don't actually do that in practice. You do this not because this is simple, not to create a better user experience but so that you can have 100+ teams working on the site without them being stuck because every change needs to be carefully coordinated with everyone else.
- rco8786 9y agoCould you expand on that last bit? If I’m working on one part of the site and someone else is working on another, what sort of coordination problems do we have? If we’re both working on the same part, sure, but it’s not clear to me how the approach laid out in OP fixes that?