... the answer would depend on which street corner you asked.

> people seem so unaware of how idiosyncratic their preferences are

Yes, they are. They also tend to state that "most people" agree with them. This is called subjectivity.

If a website offers me the choice between "accept cookies" and "more options", I'll manually edit the DOM to remove the popup from the offending website. Some sites disable scrolling while such a "We value your privacy" popup is shown, so I wrote a js bookmarklet to work around most common means of scroll hijacking.

Google is currently waging a war against adblockers, especially on youtube. I currently have a way around that too but should they start baking ads in the video bytes, I'll stop using youtube altogether (though I am willing to look the other way for content creators shouting out their curated sponsors).

There is simply no universe in which I pay for certain types of digital content, and while I can't stop the data collection that ultimately pays for it, I can at least make damn sure that it's unlawful.

With respect to Spain and sports, stadiums are littered with ads, players wear ads, the commentator stream itself has ads baked in and people buy tickets and tapas to watch the game live. If that's not enough, go fuck yourselves!

HN: > created: 1 day ago

https://asciinema.org/~user%3A281302 > Joined on February 9, 2026

pipejosh is totally a real person!

Because a plumber would definitely first and foremost plug his AI software and not his plumbing company, which definitely exists!

How does this make it to the frontpage in <1 hour from posting?

P.S. https://pipelab.org/ has a bad cert

I guess that it's not as important when you're explicitly willing to pay the piper and run the full log2n iterations just for the sake of branch predictability.

Thanks for the algo though, before today I never would've thought about doing a branchless downheap with i = i<<1 + h[i<<1] != h[i]

At best you were off by one but in the context of performance, you'd want to assign that extra to a super-root of ±inf in order to save log2n extra range checks per heap-up, no?

Tell me you use -fno-strict-aliasing without telling me.

Fwiw, I agree with you and we're in good[citation needed] company: https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg...

https://news.ycombinator.com/item?id=38365892

I might tweak the UI to let users explicitly opt into no-storage operation, though now I wonder whether opening it in incognito is the correct UX approach for that behavior?

I initially wanted to go with inplainsight dot net cause that felt more fitting, but that's parked and the owner won't let it go for less than the low 4 figures, which was outside my budget for a hobby project

My main takeaway is that, for all of its footguns, React has solved a lot more problems than it created: Even for this rather simple app, the number of invariants that need to be preserved is large enough that doing jQuery-style UX feels like hand-writing assembly. I know from other projects that React's performance is quite a thorny issue, though I now wonder if that's because we're treating it as a library (as advertised) when instead we should maybe treat it as an optimizing compiler for a far too liberal language (there's only so much you can optimize when some