And this isn’t just registry data, but also the big surgery they keep doing every year.
-
-
Our survey didn't actually ask about web components! The 2018 State of JavaScript survey did: https://2018.stateofjs.com/front-end-frameworks/other-libraries/ … It came in at what appears to be 0.2% usage versus 65% for React.
2 replies 0 retweets 1 like -
Our stats for runtime usage are very different
1 reply 0 retweets 4 likes -
Are you allowed to share them?
1 reply 0 retweets 2 likes -
Lots of the per-feature UMA is public via http://chromestatus.com : https://www.chromestatus.com/metrics/feature/timeline/popularity/457 … https://www.chromestatus.com/metrics/feature/timeline/popularity/1689 … https://www.chromestatus.com/metrics/feature/timeline/popularity/804 … Lots of noise and variability from lots of sources, but for some context: https://www.chromestatus.com/metrics/css/timeline/popularity/242 …
1 reply 0 retweets 5 likes -
Replying to @slightlylate @seldo and
Lots of ways to understand/debate these: - relatively few, very large sites driving WC usage? (e.g. http://yt.com ) - lots of use NOT represented in NPM? (e.g. AMP) - WC usage is compatible with other frameworks, so folks can be "using Preact", but composing CEs
1 reply 0 retweets 4 likes -
Replying to @slightlylate @seldo and
The last one is undersold, IMO. We've seen ad networks using WC, sites implementing small fragments using them (as part of a design-system), etc. Composition is enabled by metal-level compatibility through DOM.
1 reply 0 retweets 3 likes -
This is very interesting data, thank you! It would certainly be interesting to break it down by %age of domains, say, rather than %age of traffic.
2 replies 0 retweets 2 likes -
Yeah, and that data is harder to get. I also worry about enterprise-blindness. Most big-cos turn off the infra that reports these numbers, so things like Salesforce moving hundreds of thousands of developers to WC is worryingly invisible to us: https://developer.salesforce.com/docs/component-library/documentation/lwc …
2 replies 1 retweet 7 likes -
Replying to @slightlylate @seldo and
well said, this. this is a bigger problem than I even realized if you're saying you can't even get anon reporting/instrumentation from them?
1 reply 0 retweets 1 like
Correct. Enterprises generally turn off metrics and crash reporting via policy: https://www.chromium.org/administrators/policy-list-3#MetricsReportingEnabled …
-
-
Replying to @slightlylate @briankardell and
Could we do a marketing push to enterprises to say that if they want Chrome to know what features are important to them, what to invest in, etc. that they should turn metrics on?
1 reply 0 retweets 5 likes -
Replying to @justinfagnani @slightlylate and
Yeah.. am kind of sad now about the many times I have said browser instrumentation could be the thing we need to provide this and nobody pointed this out to me :( Good to know. How do we become good dictionary editors if we can't see 80% of language use?
1 reply 0 retweets 4 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.