Go 1.27 introduces a goroutine leak profiler to detect goroutines permanently blocked on channels or sync primitives in production systems, addressing limitations of existing tools like goleak and synctest that cannot reliably identify leaks at scale or distinguish them from temporarily blocked goroutines.
An EFF analysis of Flock Safety automated license plate reader (ALPR) search logs reveals that police officers across the United States are abusing mass surveillance systems by conducting searches with frivolous or nonsensical justifications like 'LOL,' 'LMAO,' 'sexy,' and 'idk.' Despite vendor claims of improved safeguards, the systems lack warrant requirements and meaningful audit processes, enabling officers to track citizens' locations for personal whims, stalking, ethnic profiling, and trivial complaints.
This post chronicles five years of JavaScript on WebAssembly development (2021–2026), focusing on Javy, a toolchain designed to run untrusted JavaScript code server-side on WebAssembly. Key milestones include Javy's creation in 2021, achieving production-readiness in 2022, moving to community governance under the Bytecode Alliance in 2023, adding profiling capabilities in 2024, and improving extensibility in 2025.
A developer created buildprof, an open-source Linux tracing tool that visualizes compile times by showing process timelines during builds. The tool was inspired by investigating why Bun's Rust build was reportedly 5× faster than its previous Zig build, revealing how factors like compiler choice and link-time optimization strategies affect build performance.
An article demonstrating how to identify performance bottlenecks in a Flask shop application using Wrapture, a tool that traces method calls and measures both total time and self-time (time spent in the method itself versus its children). The example shows that while an /order endpoint takes 37ms total, the Ledger.record call accounts for most of that time, enabling developers to pinpoint which component is actually slow.
JetBrains discovered that Microsoft Defender was causing unexpectedly slow startup times for Rider and ReSharper on Windows when they adopted an out-of-process architecture. Working with Microsoft, they profiled the issue using ETW logs and found that processes outside write-protected paths received full scans adding tens of seconds to launch. JetBrains developed tools to measure and investigate this impact across developer tools.