
Sam Richard
@Snugug
BBQ lead, ChromeOS DevRel. Mostly food, sometimes design and development, especially for the web. 7008px tall. He/him.
An archive of my Twitter timeline up until I moved to Mastodon. You can find me there at @[email protected]
-
@jaffathecake Although now that I’m reading through caniuse it looks like it the only multi-vendor imp was the final one
-
@jaffathecake multiple implementations happening all following a standard and then that changing in non-compatible ways
-
@jaffathecake What concerns me about that definition is getting burned by something like flexbox again, but understand the goal
-
@jaffathecake Not that I don’t love what’s happening, just a question about how “standards” are understood.
-
@jaffathecake So if it’s only supported in Chrome? Or more extreme, only supported in Chrome and not on roadmap anywhere else?
-
#ChromeDevSummit Tough Question: Isn’t that a Google experiment at that point? Not a standard? 2/2
-
#ChromeDevSummit Tough Question: How does Google rectify saying things are open standards when only Google supports it and is in Draft? 1/2
-
@thealphanerd @Una @DogpatchJS cupertino. The CDS party is tonight!
-
The main security takeaway from #ChromeDevSummit is: you wanna do something besides send a user text? HTTPS. Even then, HTTPS.
-
RT @ChromiumDev: Physical Web is now available in Chrome DEV, hear more at the #ChromeDevSummit: g.co/chromedevsummit https://t.co/uF1BE…
-
RT @tkadlec: Awww yeaaaahh… #chromedevsummit @ThePhysicalWeb
SO excited about this!
-
@addyosmani @gauntface Us IBMers are sitting here, nodding, taking notes for things to bring back. This will be one of them.
-
RT @addyosmani: @Snugug and Mr. @gauntface :) It’s been fun playing with app shell techniques for the last few weeks 🎈
-
Vanilla JS app shell demo by @addyosmani for working with service workers. #ChromeDevSummit
-
Service workers need to be treated as progressive enhancement. First view will never have, same w/old browsers. #ChromeDevSummit