250MWh 'Sand Battery' to start construction in Finland
energy-storage.news
LinkedIn is loud, and corporate is hell
ramones.dev
Vsora Jotunn-8 5nm European inference chip
vsora.com
Same-day upstream Linux support for Snapdragon 8 Elite Gen 5
qualcomm.com
How Charles M Schulz created Charlie Brown and Snoopy (2024)
bbc.com
Physicists drive antihydrogen breakthrough at CERN
phys.org
Underrated reasons to be thankful V
dynomight.net
A Programmer-Friendly I/O Abstraction Over io_uring and kqueue
tigerbeetle.com
Tell HN: Happy Thanksgiving
DeepSeekMath-V2: Towards Self-Verifiable Mathematical Reasoning [pdf]
github.com
Indie, Alone, and Figuring It Out
danijelavrzan.com
TPUs vs. GPUs and why Google is positioned to win AI race in the long term
uncoveralpha.com
Inspired by Spider-Man, scientists recreate web-slinging technology
scienceclock.com
Show HN: Runprompt – run .prompt files from the command line
github.com
Modelling Agent Systems with Erlang (2004) [pdf]
erlang.org
The VanDersarl Blériot: a 1911 airplane homebuilt by teenage brothers (2017)
historynet.com
Coq: The World's Best Macro Assembler? (2013) [pdf]
nickbenton.name
> You can switch a file descriptor into non-blocking mode so the call won’t block while data you requested is not available. But system calls are still expensive, incurring context switches and cache misses. In fact, networks and disks have become so fast that these costs can start to approach the cost of doing the I/O itself. For the duration of time a file descriptor is unable to read or write, you don’t want to waste time continuously retrying read or write system calls.
O_NONBLOCK basically doesn't do anything for file-based file-descriptions - a file is always considered "ready" for I/O.