I'd rather read the prompt
claytonwramsey.com
The complicated business of electing a Doge
theballotboy.com
Dummy's Guide to Modern LLM Sampling
rentry.co
KaiPod Learning (YC S21) Is Hiring VP of Engineering
ycombinator.com
The Alabama Landline That Keeps Ringing
oxfordamerican.org
Minimal Linux Bootloader
raw.githubusercontent.com
Critical Program Reading (1975) [video]
youtube.com
TScale – distributed training on consumer GPUs
github.com
In kids, EEG monitoring of consciousness safely reduces anesthetic use
news.mit.edu
Evidence of controversial Planet 9 uncovered in sky surveys taken 23 years apart
space.com
Technical analysis of TM SGNL, the unofficial Signal app Trump officials use
micahflee.com
Show HN: EZ-TRAK Satellite Hand Tracking Suite
github.com
The Merovingians: 'Do-Nothing Kings'?
historytoday.com
Thunderscope update: My take: Why open source is better
crowdsupply.com
Show HN: Free, in-browser PDF editor
breezepdf.com
Gorgeous-GRUB: collection of decent community-made GRUB themes
github.com
Collections: Why Archers Didn't Volley Fire
acoup.blog
I find Clang generally a bit too eager to combine loads. This is especially bad when returning structs through the stack; you typically write them piecemeal in some function, return, and then the caller often wants to copy it from the stack into somewhere else, which it does with SIMD loads/stores.
This is a significant problem on AMD; Intel and Apple seems to be better.