Kagi Small Web

Microsoft's 'unhackable' Xbox One has been hacked by 'Bliss'

<a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20260317185928&#x2F;https:&#x2F;&#x2F;terathon.com&#x2F;blog&#x2F;decade-slug.html" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20260317185928&#x2F;https:&#x2F;&#x2F;terathon....</a>

A Decade of Slug

Python 3.15's JIT is now back on track

Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

Honda is killing its EVs

Mistral AI Releases Forge

Node.js needs a virtual file system

Unsloth Studio

Ryugu asteroid samples contain all DNA and RNA building blocks

It Took Me 30 Years to Solve This VFX Problem – Green Screen Problem [video]

Have a Fucking Website

More than 135 open hardware devices flashable with your own firmware

Edge.js: Run Node apps inside a WebAssembly sandbox

I wanted to see how fast an isolated code sandbox could start if I never had to boot a fresh VM.So instead of launching a new microVM per execution, I boot Firecracker once with Python and numpy already loaded, then snapshot the full VM state. Every execution after that creates a new KVM VM backed by a `MAP_PRIVATE` mapping of the snapshot memory, so Linux gives me copy-on-write pages automatically.That means each sandbox starts from an already-running Python process inside a real VM, runs the code, and exits.These are real KVM VMs, not containers: separate guest kernel, separate guest memory, separate page tables. When a VM writes to memory, it gets a private copy of that page.The hard part was not CoW itself. The hard part was resuming the snapshotted VM correctly.Rust, Apache 2.0.

Show HN: Sub-millisecond VM sandboxes using CoW memory forking

Why AI systems don't learn – On autonomous learning from cognitive science

The pleasures of poor product design

A tale about fixing eBPF spinlock issues in the Linux kernel

SSH has no Host header

Electron microscopy shows ‘mouse bite’ defects in semiconductors