Why Lexing and Parsing Should Be Separate

How we tracked down a Go 1.24 memory regression

Maybe the Fastest Disk Usage Program on macOS

Optimi-Zi(n)g Sudoku-Solving

Giving Benchmarks a Boat

Taming the Bias: Unbiased* Safepoint-Based Stack Walking in JFR

Parsing Protobuf like never before

Rust Clippy performance status update

Optimize CPU performance with Instruments

Activity Monitor Anatomy

The Chapel Programming Language

I designed my own fast game streaming video codec – PyroWave

SIMD.info – Reference tool for C intrinsics of all major SIMD engines

Packages proxies

Local-first search. A tale of frustrated dreams, utopian user experiences and calculated tradeoffs

PHP-ORT: Machine learning inference for the web

Async I/O on Linux in databases

Strategies for Fast Lexers

Test results for AMD Zen 5

The Sparse Frontier: Sparse Attention Trade-offs in Transformer LLMs

Show HN: Timep – a next-gen profiler and flamegraph-generator for bash code

You Must Do This 5‑Minute Postgres Performance Checkup

Another Google Pixel 6a catches fire after battery-nerfing update | Google's Battery Performance Program update was supposed to stop this.

Optimizing a Math Expression Parser in Rust

Compression Dictionary Transport

Parallelizing the physics solver

Efficiency of a sparse hash table

What do you feel Rust is not a good option for? Like a general back-end where performance is fine with a Garbage Collector? Something like that, whether Rust would still be a great option or not.

500× faster: Four different ways to speed up your code

Scientists uncover key to stable, high-performance, and long-life sodium-ion batteries

More →