Myocardial infarction may be an infectious disease
tuni.fi
If my kids excel, will they move away?
jeffreybigham.com
Pass: Unix Password Manager
passwordstore.org
Show HN: A store that generates products from anything you type in search
anycrap.shop
Two Slice, a font that's only 2px tall
joefatula.com
AMD's RDNA4 GPU Architecture at Hot Chips 2025
chipsandcheese.com
Recreating the US time zone situation
rachelbythebay.com
Lexy: A parser combinator library for C++17
github.com
RFC9460: SVCB and HTTPS DNS Records
datatracker.ietf.org
The Socratic Journal Method: A Simple Journaling Method That Works
mindthenerd.com
Presence in VR should show tiny people, not user avatars
interconnected.org
Adding OR logic forced us to confront why users preferred raw SQL
signoz.io
486Tang – 486 on a credit-card-sized FPGA board
nand2mario.github.io
How the restoration of ancient Babylon is drawing tourists back to Iraq
theartnewspaper.com
Safe C++ proposal is not being continued
sibellavia.lol
How Ruby executes JIT code
railsatscale.com
Orange rivers signal toxic shift in Arctic wilderness
news.ucr.edu
Four-year wedding crasher mystery solved
theguardian.com
EFF to court: The Supreme Court must rein in secondary copyright liability
eff.org
My first impressions of gleam
mtlynch.io
SkiftOS: A hobby OS built from scratch using C/C++ for ARM, x86, and RISC-V
skiftos.org
Wayland breaks the tools I use to make a living
rykarn.se
The case against social media is stronger than you think
arachnemag.substack.com
This appears to avoid one of the classic bugs with parser combinators (expensive backtracking and/or memory-use), but appears not to fix one of the other catastrophes.
To be explicit: one of the "features" this advertises is equivalent to saying "if you stop compiling your code with `-Wall`, you don't have to deal with all those pesky warnings!"