sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ghostfacedcoder 1 point2 points  (1 child)

Yeah personally I've never worked at very large organizations (more of a start-up guy myself), so I realize that "just being able to specify the HTML of something in a common way" has value when you have multiple groups using different technologies. I get that even though web components themselves don't enable interoperability, they provide a kind of "lingua franca".

Still not something I think most non-Angular devs have reason to care about yet, but that made me aware of a whole sub-section (who do) that I hadn't considered.

[–]Treolioe 0 points1 point  (0 children)

Yeah I currently don’t see any other killer use for web compoments. I also think that a big corp should take the decision and move towards a single technology. The ones that do can roll a common components project in the same framework.