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

Node.js needs a virtual file system

Meta and TikTok let harmful content rise to drove engagement, say whistleblowers

Honda is killing its EVs

Get Shit Done: A Meta-Prompting, Context Engineering and Spec-Driven Dev System

Ryugu asteroid samples contain all DNA and RNA building blocks

Java 26 is here

OpenSUSE Kalpa

Unsloth Studio

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

Mistral AI Releases Forge

'The Secret Agent': Exploring a Vibrant, yet Violent Brazil (2025)

Edge.js: Run Node apps inside a WebAssembly sandbox

Chrome extension adjusts video speed based on how fast the speaker is talking

Tabs, splits, and tmux work fine until you have several projects open with logs, tests, and long-running shells. I kept rebuilding context instead of resuming work. Horizon puts shells on an infinite canvas. You can arrange them into workspaces and reopen later with layout, scrollback, and history intact.Built in 3 days with Claude&#x2F;Codex, dogfooding the workflow as I went. Feedback and contributions welcome.

Show HN: Horizon – GPU-accelerated infinite-canvas terminal in Rust

Torturing Rustc by Emulating HKTs

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