Note archive: October 3rd, 2019

Replying to a tweet from @gregwhitworth

I was quoting @Zeynep from the Web At 30 event earlier this year.

Replying to a tweet from @xhafan

Oh, yes, Turbolinks is very exciting!

…at least until @JaffaTheCake’s proposal for navigation transitions becomes a reality:

https://github.com/jakearchibald/navigation-transitions

(and no, Portals definitely don’t cut it here).

Replying to a tweet from @ChrisFerdinandi

I agree that Chrome has the edge on Firefox for JavaScript work (while Firefox definitely leads in CSS tooling) …but a little birdie from Mozilla told me that some exciting improvements are coming soon!

Replying to a tweet from @JoubranJad

Oh, I see! I thought you were saying that an app shell is a prerequisite for any good progressive web app.

Replying to a tweet from @JoubranJad

Totally agree that getting something on the screen as quickly as possible is a prerequisite …but an app shell is not the only way to do that. Conflating the two is confusing.

Replying to a tweet from @JoubranJad

But if you agree it’s not the only way, why did you describe it as a prerequisite?

It’s 2019 and Safari only supports the CSS clip-path property with a -webkit prefix.

It has been this way for over five years now.

Death to vendor prefixes!

If the pinnacle of our ambition when building for the web on mobile is to imitate native apps, we have set our sights way too low.

https://adactio.com/journal/11130

Listening to @JoubranJad’s @FronteersConf talk, and I’m afraid I fundamentally disagree with his assertion that an app shell is a prerequisite for a good progressive web app. It’s one approach. Other excellent approaches are available.

map

Checked in at Pathé Tuschinski. Fronteers — with Remy, Phil