There's a lot of strategy, growth projection work, and brand identity wrapped up in answering this. But we don't need to do that work. In basically zero of the teams I've worked with has there *ever* been a hard tradeoff. *NOBODY* is anywhere *near* the richness/reach frontier.
-
-
Replying to @slightlylate @SlexAxton
In every single case, doing better for everyone does better for the business. Why? Doesn't actually matter. Could be marginal buyer. Could be better service to core market. Does. Not. Matter. The idea we need all this script to deliver richness is a straight-up lie.
1 reply 2 retweets 3 likes -
Replying to @slightlylate @SlexAxton
So who's lying and why? Well, some folks honestly believe this tosh. They've been sold a bill of goods and I feel sorry for the users they're trying to reach. Some are leaning into their priors and are afraid to admit the mountain of evidence that shows lowered lifetime value.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @SlexAxton
That is, very few folks waving the JS flag want to ever talk about or describe the remediation journeys I see so many of. I tip my cap to Aldo for coming (sort of) clean on the work required once you've persistently destroyed your UX with "modern" frontend.
1 reply 0 retweets 1 like -
Replying to @slightlylate @SlexAxton
*some* folks -- the really dangerous ones -- lie by omission. They'll say "X works for us here at BigCo" without describing necessary lateral investments: perf teams, CIs, size/latency budgets, deep analysis pipelines...and totally separate desktop/mobile/"lite" versions.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @SlexAxton
If they, instead, said "with the appropriate guardrails, X works for us in reaching a subset of our users", it'd be a less compelling sell. Their OSS careers might be hurt. Their tools might not "win". But they'd sleep better, I reckon.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @SlexAxton
The JS community seems to (want to be seen to) care about every sort of diversity except delivering experiences to a diverse set of users. The disconnect turns my stomach.
1 reply 1 retweet 6 likes -
Replying to @slightlylate @SlexAxton
i get your JS is heavy and un-inclusive point but what is a credible alternative for building modern/"snappy" webapps at early stage? Plain text like https://motherfuckingwebsite.com/ ? And when in need of auth + multilanguage + "fetch this data in external API feat" ? (ping
@cpclermont)2 replies 0 retweets 0 likes -
Replying to @Francoolaami @slightlylate and
Preact is a good choice. We used it in http://squoosh.app and http://proxx.app , both are interactive in under 5s on 2G. Its not about being tiny everywhere. Its about the payload for interactivity being tiny. With react you often lose before the race has begun.
1 reply 0 retweets 3 likes -
Replying to @DasSurma @slightlylate and
nice ! i was shower deciding 48h ago to set my baselines for web dev tests at 2G internet speed. Any tooling to enforce that line of thought ? at Ci level, does preact helps ?pic.twitter.com/SoOaWAvouZ
1 reply 0 retweets 0 likes
See also, Lit, Stencil, Hyper, Dojo, Skate, and Svelte.
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.