iiiggglll

Wow, what city is this?

> I've filed bugs

Was that using Radar? Did you try using the "Report an Issue" UI within the Maps app itself?

One of the perl guys (maybe Larry Wall?) said the same thing at a talk once about companies using perl but not wanting anyone to know it because it was a such a time saver they considered it a competitive advantage.

Welcome to the 21st century, where quality, accuracy, and precision are sacrificed at the altar of "scale".

I'm not so sure. Developers may be excited at the chance to forgo the App Store / Play Store, but will users get onboard? They've had 10 years of training to download an app from a store. Will the flow for onboarding with a PWA be a complement to that, or just create confusion?

I agree with most of what you wrote, and I do think it was the right call for them to implement this feature for iPhones with batteries having trouble, and I agree most if not all the articles about this have been poorly written and badly misinformed. However...

> for the "Apple should have been transparent" crowd, here's what it said in the release notes

I can't agree that that's sufficient. That little one liner in the release notes just isn't enough.

On macOS, they did more. The battery menu extra will actually display a warning when clicked if it detects that your battery is having trouble. It shows as an extra row at the top of the drop-down menu with a little little caution triangle icon and the string "Service Battery". When you click this, it takes you to a help article advising you to "take your computer in for service". It's not perfect, but it's better than not telling the user anything.

Apple could and should have done something similar on iOS, especially given that there's a whole section in Settings for just the battery. They could have displayed a similar alert icon with similar help text, for starters. A full-screen alert advising the user to get their battery serviced whenever this condition was detected would have been even better. Burying it as a single sentence in the release notes wasn't all that helpful or informative for customers.

> A third line of attack is likely to become important soon, perhaps as soon as next year. Former Facebook executive (yes, another dissident insider) Antonio Garcia-Martinez argued earlier this year that Facebook's ad targeting based on data collected from users is essentially unethical (and also that Facebook oversells its targeting ability).

That last parenthetical about overselling points to a fourth line of attack: fraud. There's been a lot of rumbling for years that FB (and Google for that matter) are not doing enough to combat fake clicks / views / likes and are essentially ripping off advertisers. If everyone smells blood in the water all of a sudden due to these other issues heating up, there could be a lot of pressure on these companies to provide more transparency. That could bring their revenues way down.

This will only become more common once vehicles are self-driving. People will live in their vehicles and have them either drive around all night or find a place to park many hours away from their jobs (assuming there any jobs left).

The fantasy many folks seem to have about self-driving vehicles causing car ownership to disappear in favor of automated Ubers/Lyfts/whatevers on demand might come to pass for one class of people, but there will be large numbers of people for whom the opposite happens: they give up their homes (by choice or not) and live in a self-driving vehicle that is the only dwelling they own.

> Besides the big 3, I also froze reporting from Innovis.

Why Innovis? Who typically uses their reports?

> Even though Apple had not ironed out many of the basics, like how the autonomous systems would work, a team had already started working on an operating system software called CarOS. There was fierce debate about whether it should be programmed using Swift, Apple’s own programming language, or the industry standard, C++.

Wow. Few things guarantee success like starting off a project with a good old-fashioned language flamewar!