Microfrontends: how can we optimize only for developers to the n'th degree. Throwing away performance, UI/AX consistency, and predicable design out the door (dramatic). If, we were still doing systems programming microfrontends makes sense. But this is the web. Diff constraints
-
-
...and then you are tightly coupled to a react version. When grown big, it is very difficult to upgrade when it comes to breaking changes in the core lib.
-
Basically everybody has a `peerDependency` on `react`. You upgrade the version of React on the main consuming application, and then let everybody start using new React features in their micro-frontends in their own time.
- 4 more replies
New conversation -
-
-
Then it's not so different from installing a library from the internet but just with 'application features'. This way of working allows a team to diverge in their approach and deploy their individual feature separately. But they must share code to appear within the same app.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Sure. I don’t call that micro-front ends because it’s literally indistinguishable from how we always wrote React code. I’m not familiar with others way to write React.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.