WebComponents App Architecture

[niranjan.r...@gmail.com]

I am trying to get my head around WebComponents and Potential Enterprise application architecture options. I went through the videos and articles on the polymersJS and Mozilla's brick and Microsoft's WinJS. I am mostly looking at these from a packaged apps perspective not as much from website creation.

I am trying to get a 5000 foot view with out getting caught-up in the fine details. It feels like webcomponents are similar to winforms/vbx/ocx/.net controls redone using web technologies. Am I thinking about this correctly?

Based on the historical perspective, I am thinking potential higher level application frameworks and architectures might be

1. Event Driven - ( old windows form model, polymerjs samples seems to be using event driven model)
2. MV*(C) - (guessing AngularJS 2.0 proposed view of the world - use the plumbing from web component infrastructure and create a higher level MVC framework )
3. MV*(VM) - WinJS seems be going there, they are creating their proprietary controls now, I am hoping they will move to webcomponents as they mature

I am not trying to say these are the only frameworks out there. I am using them as examples think about the impact and future direction for a mental model.

Please help me by correcting my understanding or additional things I have not thought about.

Thanks, 

Niranjan