FWIW, the difficulty level in "adding something to HTML" and "adding a low-level API to enable userspace" isn't much different; but the impacts are massively divergent...which is why we wrotehttps://github.com/extensibleweb/manifesto …
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @groby @stubbornella and
This is part of why the infrastructure we've built out for Web Components is so damned important, e.g. Constructable Stylesheets, `::part`, Form Participation, etc. etc. You can't build things up in userspace at reasonable cost until the platform spills its guts.
1 reply 1 retweet 6 likes -
Replying to @slightlylate @groby and
...so what we have today, is libraries doing FAR too much in userland, undercutting the platform's basic value proposition (lightweightness, ephemerality, ability to work at the low-end). Our developers are drowning the web in script because we didn't put the gas on WC infra.
3 replies 0 retweets 4 likes -
Replying to @slightlylate @groby and
I’ve never understood why WC are a panacea to bundle size issues... doesn’t feel like that logically follows.
1 reply 0 retweets 3 likes -
Replying to @stubbornella @groby and
They're not? But WC don't create an alternative JS-first universe where you can't rely on the platform for anything (and therefore don't). Look at all the legacy support code in the most popular tools; it's all redundant when you start from the modern platform. Pure tax.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @stubbornella and
A different frame: what cost is too high? It depends! If there aren't any public services and you don't get anything "for free", then you pay what you pay. If, OTOH, there's an easily-accessible, functional thing built-in, replicating in userland is suddenly "too expensive".
1 reply 0 retweets 2 likes -
Replying to @slightlylate @stubbornella and
So are todays' successful frameworks "too expensive" from a 2011 perspective? Nope! Are they nonsensical from a 2019 perspective? You bet.
2 replies 0 retweets 3 likes -
Replying to @slightlylate @stubbornella and
Polymer shrinking between V1 and V2/3 and polyfills becoming *less* necessary for most users is such a great example of this: when the platform rises up to meet you, the effective tax rate goes down, instead of staying constant.
1 reply 0 retweets 5 likes
None of this would matter if CPUs were uniformly getting faster, but low-end mobile is *happening*, so tools grown in the NPM/latest-iPhone/2010-framework-assumption privilege bubble aren't working.
-
-
Replying to @slightlylate @stubbornella and
You can make messes with any toolchain. This isn't about absolutes; it's a probability distribution. And tools that come from the privilege bubble are *more likely* to hose users and teams.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @stubbornella and
I should caveat the claim that nobody tries to stay under budget; _statistically speaking_, nobody is trying to stay under a global budget. A few early adopters are and they're doing a great job. Some are saddled with privilege-bubble tools, tho; yields an enormous tax rate.
1 reply 0 retweets 3 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.