tripdout
tripdout on Hacker News
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.
Posted by
tripdout on Saturday September 19, 2026 @10:23PM
from the youtube.com dept.
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.
Posted by
tripdout on Thursday September 10, 2026 @04:35PM
from the phoronix.com dept.
It looks very wide in the unfolded configuration.
It looks very wide in the unfolded configuration.
Posted by
tripdout on Wednesday September 09, 2026 @01:32PM
from the ryanis.cool dept.
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.
Posted by
tripdout on Saturday September 05, 2026 @03:29PM
from the en.wikipedia.org dept.
Posted by
tripdout on Tuesday September 01, 2026 @06:33PM
from the dogbolt.org dept.
Posted by
tripdout on Sunday August 30, 2026 @11:28PM
from the data-structures-in-practice.com dept.
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?
Posted by
tripdout on Tuesday July 14, 2026 @04:07PM
from the spinningnumbers.org dept.
Well, both, probably. GrapheneOS requires a lot of framework and device side changes.
I remember seeing a video where someone was talking about how from someone on the YouTube team said that their goal is for you to to replace the word “algorithm” with “audience”.
Whether they achieve that goal or not is a different story.
Posted by
tripdout on Wednesday June 03, 2026 @11:33PM
from the moonrf.com dept.
I agree I run the risk of being wrong and could at least provide some evidence, but I think at the very least it can be one additional piece of information someone could use in their consumption of this content.
Are these reasoning blobs the reason ChatGPT always requests to “store data in persistent storage”?
Does that website blocking work for browsers other than Safari?
Posted by
tripdout on Saturday May 30, 2026 @11:42PM
from the youtube.com dept.
Posted by
tripdout on Friday May 29, 2026 @04:07PM
from the scattered-thoughts.net dept.
Posted by
tripdout on Thursday May 28, 2026 @09:59PM
from the hylo-lang.org dept.
Back to Nix again? I remember one of their employees had a great video series on it, but then they stopped using it because it was too complicated.
I’m running the risk of just getting an AI response back, but:
How are you able to boot Debian from an SD card, and without unlocking the bootloader?
Does the bootloader look for an OS on SD card by default? SD and eMMC are basically the same thing, is it just the same lines but an SD card takes priority over the eMMC? And does it not enforce verified boot properly / at all? Maybe being a Rockchip and not MTK/QCOM has something to do with it, but it’s still an Android device and I would assume there’s something in CTS/VTS/GMS licensing that makes verified boot mandatory.