Tags: ep

1329

sparkline

Thursday, January 27th, 2022

Replying to

Thank you so much—I really appreciate it!

Wednesday, January 26th, 2022

Replying to

I thought Bruce worded it perfectly.

I’m curious: did you know about the #AppleBrowserBan prior to this? (I have a feeling that not many people are aware of the situation on iOS.)

Replying to

Replying to

Every browser on iOS uses the same engine as Safari. They have to. Apple won’t allow rival rendering engines in the app store.

Firefox on iOS is a skinned version of Safari.

Chrome on iOS is a skinned version of Safari.

Monday, January 24th, 2022

Replying to

Do you realise how childish you sound?

“We shipped it first, nah-na-na-nah-nah!”

Have some self-awareness. You’re better than this.

Replying to

Alex, you seem to be saying that any criticism of Safari (even if it’s unwarranted and unrelated) is justified by the rendering engine monopoly on iOS.

That’s childish. It does your/our cause more harm than good.

Interfacecritique — Olia Lialina: From My To Me

Don’t see making your own web page as a nostalgia, don’t participate in creating the netstalgia trend. What you make is a statement, an act of emancipation. You make it to continue a 25-year-old tradition of liberation.

Replying to

Sunday, January 23rd, 2022

Replying to

Then focus on that.

Replying to

Yeah, that gave me a squirmy feeling:

https://adactio.com/journal/17132

Replying to

“Banning criticism” …really?

Next you’ll be saying that Google is a victim of cancel culture.

There is absolutely a race to the bottom going on, I agree with you there. I think you won the race with your mocking off-message tweet.

Replying to

Just now:

I’m not taking them to task for accepting the work.

Three hours ago:

Please DONATE NOW to the world’s richest company, to help feed their starving browser.

Replying to

Yes! Exactly!

That’s exactly how I felt when Yoav had a crowdfunding campaign to get picture in Blink and when Agalia had a crowdfunding campaign to get :focus-visible in Webkit.

Same energy.

Replying to

I agree that Apple’s priorities are out of whack.

Take them to task for having priorities that are out of whack.

Taking them to task for accepting contributions is a distraction. It harms your case.

Replying to

And to be clear, I wrote at the time that crowdfunding accessibility features feels wrong:

https://adactio.com/journal/17132

But my concerns would be hypocritical if I worked on a browser that accepts crowdfunded contributions.

Replying to

It’s really not a good look when you’re pissing on other browser makers shipping something, especially when the behaviour you’re mocking is only nit-pickingly different from your own empoyer’s behaviour.

And by “you” I don’t mean Google.

Replying to

It absolutely was a whip-around.

If a browser maker accepts crowdfunded contributions, great. But then to later mock other browser markers for also accepting crowdfunded contributions? Not great.

Replying to

Saturday, January 22nd, 2022

Replying to

Replying to

Got it.

Kind of like how Chromium and Webkit are playing catch-up to Gecko’s leadership on subgrid.

(Let me know if there’s a tip jar for that so I can toss in a coin or two.)