miniblog.

It's incredibly hard to explain adversarial problems to users. I see gamers sincerely asking "why doesn't the publisher just fix the cheater problem?". This is exacerbated by the fact that sharing too many details of anticheat can make the problem worse.

A deep dive on ABI design tradeoffs, and how Swift approached the problems in this space; https://gankra.github.io/blah/swift-abi/ (Compared with C++/Rust, it avoids monomorphisation and does more boxing, with attention to details that affect performance)

$ tree-sitter parse -- '/home/wilfred/.emacs.d/**/*.el' --quiet --stat Total parses: 2272; successful parses: 2271; failed parses: 1; success percentage: 99.96% It's super easy to test a tree-sitter parser against a large corpus, and to iron out the details!