Thanks for taking the time to find/share these links! Very informative.
It sounds to me like most of the criticism's outlined are solvable. Perhaps the people behind the standard should be engaging the framework community more.
I wonder if you think web components (and the problem they set out to solve) is wrong from a fundamental/architectural standpoint?
Web components seem like a good idea to me. I would imagine there are a lot of libraries out there (eg/ calendars, styling frameworks) that would benefit from reuse across applications. The browser could cache it even if served from a different CDN.
I'm curious what the problems are with web components that you see? Is it specifically related to how they might be used (or useless) in the major frameworks?
Frameworks like react/angular/backbone/vue solve the problem of creating a single page application with a nice architecture and sharing code between components within the SPA.
Web components solve the problem of sharing code between any application.
There are opportunities to share code (eg/ data binding) and I believe that is the case (they use the same underlying browser APIs where available)
A few years back I did something called 'master the mainframe' where they provided a TSO login for you on an instance running in one of their labs. They also provided you with a bunch of fun exercises to learn more about the system.
I love the idea of requiring the purchase of merchandise beforehand, although I'm not sure if this would only compound the problem of scalping. The problem with building moats is
a ) scalpers will write algorithms to predict where the moats are before fans can get there
I believe the problem they cited with this approach is it provides a poor UX where someone would have to keep checking the site to see if the ticket price has hit their desired target.
It would also still leave room for bots front running although still a better solution since the effects are dampened. Still, it's a lot easier for a bot to watch for a 'good price' to come up than a 'true fan'.
Perhaps to get around that there could also be an ability to make automatic purchases for a user once the ticket price reaches desired target? Something like a batch auction that randomizes winners in a cohort might work.
There are also people working in this area that would like to simply prevent resales. The problem there is it also might discourage purchases since people might be more reluctant to make such a big purchase if there is no way to recoup their money in case something happens that prevents them from going.
Perhaps another alternative to discourage scalping is if there was an identity system that requires each ticket holder to prove their identity. That, however, would also decrease the UX dramatically and would be a tough sell. But maybe the time is right to make such a hard sell?
It sounds to me like most of the criticism's outlined are solvable. Perhaps the people behind the standard should be engaging the framework community more.
I wonder if you think web components (and the problem they set out to solve) is wrong from a fundamental/architectural standpoint?