DEV Community

loading...

Discussion on: Micro Frontends: a deep dive into the latest industry trend.

Collapse
khrome83 profile image
Zane Milakovic

I am sorry, but this is a organizational issue hiding behind “framework locking” and other phrases.

You are investing in more technology....

The user is downloading more things....

The techniques and lessons learned are less shared...

And you claim you can make it all work with web components, which has there own massive set of issue....

This is a solution developed by enterprises that can’t get there shit together. This is a technical problem masking a organizational one.

  1. There is no such thing as framework lock-in that you need micro frontend to solve. You can just solve it.

  2. This usually comes about because you have a structure that has dozens of teams owning incredibly small pieces of a site. Typically the company is hiring java devs and asking them to write the front end in this case...

  3. You can’t make the argument this is ok, just because we can use web components. Web components are for sure not ready for prime time for a amazing long list of reasons. Does the browsers have some level of support, yep. Is it a good developer experience, nope. Does it force more things into Javascript making the bundles worse, yep....

As a organization, just learn how to craft a good front end. Actually hire front end engineers. Build solid components and work on communication. Don’t claim because you use three frameworks you don’t have framework login. You just have disagreement and disorganization.