Parse, Don’t Validate AKA Some C Safety Tips (via telemachus) — discussion

#c

Velocity Is Dead: AI-Generated Compilers and the Future of Software (via typesanitizer) — discussion

#vibecoding

Running RISC-V in a VM to test my snaps (via raymii) — discussion

#virtualization

How Taalas "prints" LLM onto a chip? (via Yogthos) — discussion

#ai #hardware

UTS #39: Unicode Security Mechanisms (via kana) — discussion

#programming #security

You are not left behind (via BinaryIgor) — discussion

#practices

Accessibility Is Civil Rights. AI Must Stop Shipping Barriers (via dbushell) — discussion

#a11y #vibecoding

Cosmologically Unique IDs (via hongminhee) — discussion

#distributed

ASK: Proposal: add "AI generated" as a flag reason (by danderson)

#meta

HTTP/3 on FreeBSD: Getting QUIC Working with nginx in a Bastille Jail (via fanf) — discussion

#freebsd

How We Fixed YAML Comment Preservation in Ruby (And Why We Sponsored It) (via nogweii) — discussion

#ruby

cl-kawa: A Turducken of Programming Languages (by atgreen) — discussion

#java #lisp

Fix your tools (by wofo) — discussion

#debugging #programming

A 'frozen' dictionary for Python (via ryan-duve) — discussion

#python

The Future of Math Research in the Age of AI (via jkopin) — discussion

#math #vibecoding

How and Why Local LLMs Perform On Framework 13 AMD Strix Point (by msf) — discussion

#hardware #testing #vibecoding

Hemmi/Post 1460 Versalog (Sliderule emulator) (via cyplo) — discussion

#math

Loon — A LISP that flies (via vulcan) — discussion

#lisp #wasm

ThunderKittens 2.0: Even Faster Kernels for Your GPUs (via mikejsavage) — discussion

#performance

DUMPLING: Fine-grained Differential JavaScript Engine Fuzzing (via fanf) — discussion

#javascript