Micro frontends with Stacker
dev.betterdoc.org
Micro frontends with Stacker
1–10 of 24 posts
Re: Micro frontends with Stacker
#2Betterdoc.org website is in German. Hard to find info.
Re: Micro frontends with Stacker
#3Would be nice to get a link to "Stacker" Betterdoc.org website is in German. Hard to find info.
The web page is in german because we are serving german-speaking countries.
Re: Micro frontends with Stacker
#4Re: Micro frontends with Stacker
#5Stacker, to me, will always be the DOS hard drive compression software that Microsoft stole. [1] 1. https://en.wikipedia.org/wiki/Stac_Electronics
Re: Micro frontends with Stacker
#6Once webpack 5 adds support for this, I see a lot more folks using it.
Like electron, the performance characteristics would continue to improve in the long term, but may never be as efficient as hand rolling bundles.
Re: Micro frontends with Stacker
#7Would be nice to get a link to "Stacker" Betterdoc.org website is in German. Hard to find info.
Re: Micro frontends with Stacker
#8Micro frontends seems like a technology that's similar to Electron in a way. It gets criticised for its performance characteristics but there one can't ignore the problems it tries to solve for medium-large teams — there is a real need for it. Once webpack 5 adds support for this, I see a lot more folks using it. Like electron, the performance characteristics would continue to improve in the long term, but may never…
Re: Micro frontends with Stacker
#9Micro frontends seems like a technology that's similar to Electron in a way. It gets criticised for its performance characteristics but there one can't ignore the problems it tries to solve for medium-large teams — there is a real need for it. Once webpack 5 adds support for this, I see a lot more folks using it. Like electron, the performance characteristics would continue to improve in the long term, but may never…
Re: Micro frontends with Stacker
#10We ended up deciding that with the move to component based front end frameworks (react, storybook etc) that the overhead of this wasn't worth the benefits - every developer needs it running, along with lots of services etc.
I'd love to understand what others are thinking about composition on the front end these days. I guess the fact this just got created means that the problem we were trying to solve in 2014 still exists - so perhaps I have my answer?