51 hrs later, 846AN seems to have survived the Queensland storms.

Your nuanced thoughts on how different 'camps' think of AI is one of the most thoughtful analyses I've heard. Although, I'm squarely in the 'critical' camp, I see more an more 'average' users who are embracing synthetic text, code, image, & video tools.

If LAX had replaced the entire auto loop with a basic ground-based tram system that went to hotels, drop-offs and parking it would be so much better and have saved the airport years of construction on an overly elaborate elevated rail. But we love our cars in America!

And the code looks like this. Don't try to reproduce this, as it's intentionally meant to show how confused SwiftUI can get if you don't properly use Identifiable for dynamic rows.

Why is this a feature?

It's enough of a pain that some folks created Helm for App Store Connect.

I spoke with someone from Apple, and the .leading alignment is apparently something they're trying to default to as standard in iOS 26. (I do need someone to confirm that, however.)

The Flightradar24 feed now suggests that the aircraft did back-taxi, and it was essentially a data gap. Hopefully we'll find out more during the preliminary accident report.

There are some NOTAMs regarding work in progress on both sides of runway, but it's unclear if that's runway construction. Since VAAH does not appear to have a parallel taxiway, back-taxiing is the only way to use the full runway. None of the last 5 departures seem to have done that.

That's quite the compliment to both you and Paul. :-)