3 ms·
I think the idea is that you've already done that on the backend, and you're just extending it to the frontend.
by icebraining 9y ago
I think the idea is that you've already done that on the backend, and you're just extending it to the frontend.
- tyingq 9y agoThere are unique downsides of extending it there. Bloated downloads and less caching benefit since pages need competing frameworks. How to deal with shared elements like a cart widget or login widget. Overlap...search results and shopping pages may be very similar on an ecommerce site. Their example shows those as 2 separate teams able to make all of their own stack decisions.
- coldtea 9y agoBecause there's some misguided assumption that what fits one domain should fit the other too.