tripdout

There's also OsmAnd for mobile.

I watched the first ~10 minutes, thought "wow this guy really knows his stuff", turns out he worked on Apple's System 7 and their Human Interface Guidelines, UX director for Symbian, Google, and a bunch more stuff.

Fascinating, but sadly LLM-assisted writing.

edit: and apparently AI-generated site layout too. Either it doesn't bother me as much as the writing, or I haven't seen enough examples, but I didn't notice that.

It looks very wide in the unfolded configuration.

It looks very wide in the unfolded configuration.

I really wish I understood this, it hits a bunch of topics that I've heard of and are/sound interesting, but I don't know enough to follow it. I don't get the link between the NX bit (which I get) and speculative access.

I know this is flagged, and I know the guidelines say not to complain about tangential annoyances, but the reason given is that "they're too common to be interesting" -- but is that true about LLM-written articles? A case could be made that it will only become more true if nobody objects.

I don't know what it is about LLM writing style, but I agree, it just triggers something in my brain and I can't get myself to read it.

android-latest-release branch (Android 16 QPR2) for lunch target aosp_cf_x86_64_phone-trunk_staging-eng (Cuttlefish emulator):

> du -hs --exclude /aosp/android-latest-release/out /aosp/android-latest-release

132G /aosp/android-latest-release

> du -hs /aosp/android-latest-release/out

127G /aosp/android-latest-release/out

So ~130GB each for the compiled artifacts and the source code. It's heavy, and at times can easily fill 64GB of RAM during the build.

Why is the original pattern (with the env var in double quotes) not vulnerable? Why can you close the single quotes early but you can't just include double quotes in your title? Is it something to do with the GitHub templating?