Replace your boss before they replace you
replaceyourboss.ai
Same-day upstream Linux support for Snapdragon 8 Elite Gen 5
qualcomm.com
The Input Stack on Linux: An End-to-End Architecture Overview
venam.net
Abuse of the nullish coalescing operator in JS/TS
fredrikmalmo.com
Tell HN: Happy Thanksgiving
The VanDersarl Blériot: a 1911 airplane homebuilt by teenage brothers
historynet.com
Penpot: The Open-Source Figma
github.com
Show HN: Runprompt – run .prompt files from the command line
github.com
Pakistan says rooftop solar output to exceed grid demand in some hubs next year
reuters.com
Show HN: MkSlides – Markdown to slides with a similar workflow to MkDocs
github.com
The State of GPL Propagation to AI Models
shujisado.org
Coq: The World's Best Macro Assembler? (2013) [pdf]
nickbenton.name
Inspired by Spider-Man, scientists recreate web-slinging technology
scienceclock.com
TPUs vs. GPUs and why Google is positioned to win AI race in the long term
uncoveralpha.com
Ray Marching Soft Shadows in 2D (2020)
rykap.com
Show HN: SyncKit – Offline-first sync engine (Rust/WASM and TypeScript)
github.com
Seagate achieves 6.9TB storage capacity per platter
tomshardware.com
How is how inputs gets routed to the right window out of scope for an article that wants to describe input end to end? The fact that input events get carefully routed to the right thing is both important and a potential source of bugs if not implemented correctly.