How easy is it for a developer to "sandbox" a program?(kristaps.bsd.lv)

44 points by zdw 1 year ago | 39 comments

The V8 Sandbox(v8.dev)

249 points by todsacerdoti 2 years ago | 87 comments

Sandboxing JavaScript Code(healeycodes.com)

72 points by antidnan 3 years ago | 19 comments

Observed Agent Sandbox Bypasses(voratiq.com)

57 points by m-hodges 10 months ago | 40 comments

Sloc Cloc and Code 4.0 (scc) – Finding the files that need the most attention(boyter.org)

28 points by boyter 2 months ago | 1 comments

Making Rust supply chain attacks harder with Cackle(davidlattimore.github.io)

169 points by djoldman 3 years ago | 71 comments

Devtools must be open source(blog.exe.dev)

695 points by bryanmikaelian 2 months ago | 227 comments

Blog post by David Crawshaw on exe.dev arguing that developer tools must be open source, starting from how engineers rarely wrote software for themselves.

Fixing a bug in Google Chrome as a first-time contributor(cprimozic.net)

597 points by Ameo 2 years ago | 150 comments

A blog post recounting the author's experience fixing a bug in Chromium/Google Chrome as a first-time contributor, from building the code to code review and release.

Chrome DevTools MCP (2025)(developer.chrome.com)

563 points by xnx 7 months ago | 221 comments

Chrome for Developers blog post explaining how the Chrome DevTools MCP server lets coding agents connect to and debug a running browser session.

The Chrome VRP Panel has decided to award $250k for this report(issues.chromium.org)

473 points by alexcos 1 year ago | 253 comments

Chromium issue tracker entry for an ipcz bug letting a compromised renderer duplicate a browser process handle to escape the sandbox, marked fixed.

Bypassing Google's big anti-adblock update(0x44.xyz)

941 points by deryilz 1 year ago | 816 comments

Blog post describing a Chrome bug that let extensions keep using webRequestBlocking to bypass Manifest V3's restrictions on adblockers.

The browser's main thread is expensive(kciter.so)

408 points by kciter 1 month ago | 141 comments

A devlog post on kciter.so explaining why work on the browser's main thread is costly and how it affects web app responsiveness.