A debugging deep-dive into how an AI-assisted refactor removed a comment guarding against infinite recursion, and how React 19’s `<Activity>` component masked the bug by pre-rendering an infinite tree in memory for minutes before crashing.
Advice for web developers on how to easily use a free CDN for loading open source external assets or any GitHub-hosted resource. It’s actually old news, but I still see the HTML5shiv being included using the googlecode SVN repo link (which is NOT a CDN), even on brand new websites.
Sorry if I gave the impression I was complaining about underlines.
My personal website is a playground for ideas; it is not a product anyone payed me to build, and it is not intended to sell anything. The fixed semi-transparent nav is an attempt to balance my annoyance with fixed navs that break page down/page up functionality with the utility of having quick access to useful links (use case being “interesting post, who is this person?” or “what else have they done?”). I don’t love it, and it’s pretty bad at mobile widths, but it has the distinct advantage of preventing readers from losing their place when paging. Another commenter picked up on that: https://news.ycombinator.com/item?id=8679336
Anyways, I appreciate the criticism. Though I heartily disagree that as a result of that expirement, I cannot write about improving text underlining on the web.
A floating sidebar would still be mildly annoying, but much better than the awful header nonsense. The New York Times has plenty of money to throw at web designers, but still breaks my space bar (wiggling the pointer around after hitting SPC mostly makes it work). Please don't encourage this terrible behaviour elsewhere.
Fair enough. Of course, the counterpoint is that for others who do not have that particular reaction, the overall effect of having less intersecting lines (better separation between characters and text decorations) is one of less clutter, and, arguably, heightened readability.
