There’s a reason they were used as a poster child of a bad actor when the FTC rule was made a few years ago, before the current administration shredded it.
Heh. Yeah. My memory (also unreliable) is that people weren’t churning out blog spam articles for the Adsense when I found DI, or at least maybe only on obviously popular topics like cars or whatever.
As a small example of this stupidity, I’ve enjoyed Apple Arcade. Every time I play a game I get a big Apple Arcade splash screen. Ok.
Well now (possibly 27 beta “feature”) I now also get a little dynamic island pop-up at the same time, showing me icons for a couple other games I might like.
On the service I’m already paying for.
When I’m trying to play a game.
You know when I’m not looking for another game to play? When I start one, I already have.
I went to Apple 20+ years ago, partly because they weren’t doing this crud. Now I have no choice.
That explains why it’s so rare for a new episode to appear.
I’ve been reading (then listening) to DI forever. Not the full 20 years, because I remember reading through the entire back catalog when I first found it, but a very long time.
I didn’t care. Because to me the performance was a cost I was more than willing to pay for giving me sanity in JS land. Knowing you were passing the right types, right number of arguments, etc. Just the quality of documentation you got from having types at all above the nothing we had before was huge.
I love they’ve made it a ton faster. But I never thought about giving it up due to compiler performance.
Casey is one of three hosts on an Apple focused podcast. They’ve discussed CarPlay Ultra numerous times. He’s discussed watching the WWDC session where how it works and gets themed was first explained.
That’s very odd. I’ve used my phones with 3 different cars regularly using CarPlay every single time I drive for literally a decade without ever experiencing that.
> This was covered in the article, that’s just CarPlay Ultra
And Apple doesn’t just take it over. It requires a per-model design package the OEM makes with Apple’s help. So they can keep all their logos and design elements they care about.
They still don’t do it, as you pointed out. But it’s not like using an AppleTV to avoid the terrible built in smart TV interface. The OEM is still there.
For what it’s worth I’ve heard they’re basically identical. It’s just some two-way data and an h264 video stream. There’s a reason basically everyone supports both. Seems to be really easy.
I don’t know whether the auto makers actually forced them to be compatible or it was a choice in Google’s part to get into cars that already had CarPlay.
But it really doesn’t seem like it’s a big hassle. Most of it is probably just certification testing to be allowed to use the names/logos.
TBF for a lot of stuff they could probably just monitor the audio system to fingerprint things the way TVs do these days and sell that data even if you use android auto or CarPlay.
But they certainly get a lot more if you use their maps and entertainment apps.