“I want the web to be a platform to find the future, and not just the past.” - @slightlylate
#FronteersConf
-
Show this thread
-
Amazing.
@slightlylate comparing the mobile web to an E.L.E. https://en.wikipedia.org/wiki/Extinction_event …#FronteersConf1 reply 1 retweet 2 likesShow this thread -
“it’s time to give up on responsive design” - @slightlylate
#FronteersConf#rwd5 replies 0 retweets 4 likesShow this thread -
Replying to @HenriHelvetica @slightlylate
Provocative.
Any context available on this? I'm curious about what broke, and why it's media queries' fault1 reply 0 retweets 0 likes -
Replying to @scottjehl @HenriHelvetica
As currently practiced, it's not working. Folks think it means "use the viewport tools in devtools" not "design on a phone", and then they make choices (e.g., heavyweight, desktop-era frameworks) that sink the experience from the get-go.
1 reply 2 retweets 3 likes -
We need a new name that means "designing on a phone, then bringing that to desktop".
5 replies 0 retweets 3 likes -
Replying to @slightlylate @HenriHelvetica
I agree in that I've seen a lot of badly implemented RWD. Plenty of poorly-built sites happen to use media queries. But RWD didn't list "several megabytes of CPU-devastating JavaScript v-domination" as its 4th ingredient. It sure would help to have tools to conditionally serve JS
1 reply 0 retweets 3 likes -
Replying to @scottjehl @HenriHelvetica
I'm not *blaming* RWD, I'm only noting that the ecosystem is on fire and folks don't understand that RWD as currently practiced isn't working. Tools (including DevTools) don't highlight how this won't work out.
2 replies 1 retweet 2 likes -
Replying to @slightlylate @HenriHelvetica
Scott Jehl Retweeted Scott Jehl
Understood. Really wish I was able to see the talk. I agree that performant RWD sites are sadly not the norm. Genuinely interested in ways to better control asset delivery to pair better with experiences. (eg link[async], and dumb ideas like https://twitter.com/scottjehl/status/1174395254977519616 … )
Scott Jehl added,
1 reply 0 retweets 1 like -
We care about this a lot, and still the issue we hit in basically every client project is this new waterfall step. After a site is carefully built to render and enhance near-instantly on arrival in staging, then the tag manager is added, the A/B scripts, chat bot, personalization
1 reply 0 retweets 2 likes
yeah, and teams don't have enough leverage to say no. That's why I'm pursuing Never-Slow Mode; enlisting the browser's UI and larger ecosystem incentives seems like the only effective way forward.
-
-
You shall my sword! (Seriously, I very much want never-slow mode to become a thing. Whatever the AMP team are paying/blackmailing the search team with, do that for never-slow sites!)https://adactio.com/notes/15932
0 replies 0 retweets 4 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Replying to @slightlylate @HenriHelvetica
I like that work so far.
I wish we had a similar user-controlled browser feature... a tethering mode. Like how Twitter's feature works. I'd use it on desktop as well.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.