Re: [w3c/webcomponents] HTML Modules as a leaf node in the module graph or not? (#805)

I forgot to mention another benefit of the iframe model, which I'm hoping web components can provide in a better way (while freeing us from the badly performing / overly complex client-side-centric, code-centric JavaScript monoculture which lack of HTML modules is promoting):

Although most individual workspaces got locked into a time warp due to framework lock-in, the portal container was able to switch from one popular framework to another in order to reduce the memory footprint and eliminate memory leaks, without content providers making any adjustments.  And a few workspaces got the funding to do total rewrites of themselves from one framework to another (e.g. Silverlight replacements)  It's kind of interesting that few if any workspaces ever were able to make the move from one version of the framework to the next, even, due to lack of funding and the amount of adjustments needed with each upgrade).
  
And new workspaces could be built with newer technologies (including a few with web components, which I'm hoping will break the lock-in issue just as IFrames did for the entire site)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/805#issuecomment-480898098