Valve releases Team Fortress 2 game code
github.com
A year of uv: pros, cons, and should you migrate
bitecode.dev
HP Acquires Humane's AI Software
humane.com
SWE-Lancer: a benchmark of freelance software engineering tasks from Upwork
arxiv.org
Kafka at the low end: how bad can it get?
broot.ca
Show HN: Scripton – Python IDE with built-in realtime visualizations
scripton.dev
Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
One year after switching from Java to Go
glasskube.dev
File Pilot: A file explorer built for speed with a modern, robust interface
filepilot.tech
Converge (YC S23) is hiring engineer #2 in NYC
jobs.gem.com
Nuclear fusion: WEST beats the world record for plasma duration
cea.fr
South Korean regulator accuses DeepSeek of sharing user data with ByteDance
bbc.com
Migraine is more than a headache – a rethink offers hope
nature.com
Are LLMs able to play the card game Set?
github.com
Show HN: A GPU-accelerated binary vector index
rlafuente.com
Tensor evolution: A framework for fast tensor computations using recurrences
arxiv.org
Try thinking and learning without working memory (2008)
sharpbrains.com
Why I'm writing a Scheme implementation in 2025: Async Rust
maplant.com
Making my debug build run 100x faster so that it is finally usable
gaultier.github.io
Among top researchers 10% publish at unrealistic levels, analysis finds
chemistryworld.com
Saying goodbye to FFmpegKit
tanersener.medium.com
Obviously cache snooping is going to be device-dependent, but the way this shows things happening is that if you write an address that exists in another CPU's cache, that the invalidation doesn't happen until that CPU later tries to read the address. That requires two snoop cycles be dedicated, which is a waste. The secondary CPU is already listening to the snoop bus, it can/should (and in practice does on basically all devices, AFAIK) be able to recognize that write fly by and free up its cache line preemptively.