Noticing this as well, particularly with larger Angular enterprise apps. If multiple teams are working on the same shared component, sometimes it takes days or weeks to make an update because it requires architectural meetings. Easier if everyone manages their own components.
-
-
-
Yeah, understanding how to write good components / modules can be hard. Mostly I feel because understanding the right boundaries takes experience. I wish people would / could receive more training on this!
End of conversation
New conversation -
-
-
I don't understand them at all. It's just more code to load and like wtf why would you want to work with separate frameworks at work? Seems like a huge pia
-
My understanding is that it's mostly coming from a desire to scale human resources horizontally. More & smaller teams, each responsible for an isolated part of the front end. I can empathize with that desire, but application cohesion is probably not the right thing to trade in.
- 1 more reply
New conversation -
-
-
In a small company it makes no sense. In a company of 45k with thousands of devs and hundreds of products—well, better than the alternative.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think the discussion about microfrontends should be broken into two parts: 1.the technical implementation 2.the resulting UI/UX The second would worry me a lot.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wonder what's the cost in switching between apps
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
One good thing that can come from this is forcing organizations to think about whether everything really needs to be a monolithic front end or they can *afford* to split it up and gain some freedom / manage complexity
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I would think of it from business perspective: What does it make sense from a business perspective for the user? If you also use the tactical design patterns of
#DDD to figure out, as a separate thing of the backend, the domains, subdomains and bounded contexts for the UI. -
That is Domain-driven design. And I still read the concepts and I am like: This is so freaking abstract, that I can't understand it
End of conversation
New conversation -
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.