After giving it a first, quick read it really looks like a lot of similar ideas are shared between Stacker and this framework.
Especially interesting for us is the separation between front ends on the client side, which I still, after all these years, find downright hostile if you need proper encapsulation of apps within one page.
:) see my comment -- yes, portlets are a source of inspiration for some things. As said, we need to share more to enable people to tell us if this makes sense...
Interesting that you compare Stacker to compoxure. Will need to look deeper into it, but I see a few things Stacker does in a very different way, plus it contains a lot of things compoxure seems to not touch (which, by all means, can be a good thing, please don't misunderstand me).
I only speak for us at betterdoc -- we created Stacker in order to be able to create tools that can be stacked together like containers (the real ones used for shipping things) to form various workplaces. It enables us to mix and match tools without changing code - just by configuration - and we discovered that this is not just a theoretical option, but happens regularly.
The basic idea predates 2014 by far - one of the first things I have worked on back in 2006 was a portlet server (anybody remembering this?), and now we solve many of the problems we tried to solve back then, again, with a different approach and spin.
All I can say is that working on Stacker in the last years was fun, and developing services that serve micro front ends for it gets more fun and efficient with every small step we take.
Cannot wait to share more about the ideas behind it :)