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
-
Show this thread
-
-
Replying to @dan_abramov @TheLarkInn
Probably depends on how well it's done. A lot of people mean different things by micro-frontend. In my opinion, it works quite well if every team is just producing a a React Component for each feature and another app just consumes these.
3 replies 0 retweets 3 likes -
...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.
1 reply 0 retweets 0 likes -
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.
2 replies 0 retweets 0 likes -
(Dependencies can become a pain in this solution, but only because of occasional bugs in `npm` or `yarn`.)
1 reply 0 retweets 0 likes -
No, not only bugs in npm. Consider deprecations in the main core lib.
1 reply 0 retweets 0 likes
It's not as big a problem as you think it is. The React team are very careful about providing a slow upgrade path due to the number of components at Facebook.
-
-
Of course libs are taking dev needs seriously. Especially the big ones. But what if you take your client performance really seriously and take a really small niche framework as
@hyperappJS for example. maybe they could not use that much of the runtime for backwards compat.0 replies 0 retweets 2 likesThanks. 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.