Thread by @jaffathecake

We had a lot of fun between the talks at #ChromeDevSummit. For example:

➡️ I get stuff wrong.
➡️ @DasSurma can't press buttons.
➡️ @aerotwist is a cheat.
➡️ Someone wrote a bot.
➡️ SURJIKO LIVES.

Let's dive in:

We started with the classic "we can't hearrrr you" intro. Yeah. I know. Buuuuut, check out the amazing jumpers @kosamari made.

Also, she teaches us about the "pacman circle".

We wanted to find out the audience's favourite web platform feature that launched in Chrome in the past 12 months using live-polling. But, to test things, we asked the audience the age old question: "tabs" vs "spaces". The result was incorrect.

Then we moved onto the first round: @kosamari with "Constructable stylesheets", vs @aerotwist with "Intl stuff".

…also, wait, is there a bug in the app????

Then, I get a well-deserved telling off.

This time it's me and @DasSurma. We figure out if the audience prefers "blob reading" or "custom form elements".

This vote was so close we had to sit on the floor(??).

Also @DasSurma can't use buttons.

Also also, we reveal the point of the points.

Then it's @DasSurma and @aerotwist presenting "native lazy loading" vs "backdrop filter".

Also, I make a brief appearance to deliver an important fact-check.

Turns out, I made ANOTHER MISTAKE. But, maybe I'm not the only one.

Me and @kosamari poll the audience about "Object.fromEntries" vs "Promise.allSettled".

Then, a follow-up vote becomes about hair, or the lack thereof, for reasons I still don't fully understand. Did this sway the vote?

Up this time it's @kosamari and @DasSurma with "class fields" vs "numeric separators". Two absolute titans of JavaScript functionality. But what do the audience decide?

Then @DasSurma introduces the next speaker, his personal hero.

Next, @aerotwist wears a dreadful shirt and I can barely hide my disdain.

In terms of the feature contest, it's "media keys" vs "background fetch". We genuinely picked these at random, and I was delighted to pick background fetch.

Also, wow, the follow-up vote is soooo close, and the result is genuinely surprising. That sounds click-baity, because it is, but it's also true.

Then we have @kosamari with "string.matchAll" vs @aerotwist with "web sharing".

A lowish-level JavaScript feature, vs a high level PWA feature. But what do the audience think?

It's the final two features of day 1. It's @DasSurma with "images in clipboard" vs me with "prefers styles". In terms of features, it's PWA vs CSS.

@DasSurma continues to fuck up the controls.

And here it is, the final vote of the day, where we find out the audience's favourite feature of the past 12 months. None of us expected the result.

Of course, @DasSurma presses the wrong button.

Phew ok, onto day two. @kosamari is unhappy with whoever ordered the t-shirts.

It's BigWebQuiz time again! But this time we're looking at upcoming features, starting with "contact picker" vs "idle detection", championed by @kosamari and @aerotwist.

This time it's @DasSurma and I face-off "wake lock" and "web shortcuts".

THIS ONE IS HIGH DRAMA.

Probably the most important vote of the day.

Next up, it's @DasSurma presenting "web serial", vs @aerotwist with "periodic background sync".

It's a niche hobbyist feature vs a much-requested PWA feature. But will the audience surprise us again?

This time it's @kosamari with "SMS receiver" vs me, with "CSS subgrid". The result here still blows my mind. So so close.

The next round… not so much.

Here we go, it's @kosamari with "native file system" vs @DasSurma with "content index". Two PWA features.

Yet another round that was way closer than I thought it'd be.

Next up it's me with "audio device client" vs @aerotwist with "portals".

In the face of certain defeat, I go in with a cheap shot. But does it work?

Although, we detect some foul play.

Looks have we have to rerun the previous vote. But then it's @kosamari with "image aspect ratio", vs @aerotwist "screen enumeration".

I mean, surely "image aspect ratio" can't lose??

First up, an impromptu prize-giving.

Then it's the final new features. It's me with "web bundles", vs @DasSurma with the "Raw clipboard API". Both kinda low-level features.

@DasSurma We had to take drastic action. RISE SURJIKO!

We do the final rounds of voting to find out the audience's favourite upcoming/experimental/potential feature that Chrome folks are working on.

Phew, that's it! I'm so glad I work for a team that lets us be silly, self-deprecating, and basically have this much fun *in public*.

A lot of other companies, and even other parts of Google, would shut all that down in the name of appearing 'professional'.

And finally a huge thanks to @kosamari, @DasSurma, and @aerotwist, being on stage with them is always a pleasure.

I'm a bit burned out, so I'm going to have a little holiday. Cheers!

ALL HAIL SURJIKO