another tale of go.mod bloat (via calvin) — discussion
#go
another tale of go.mod bloat (via calvin) — discussion
#go
The Future of Customer Support is Lies, I Guess (via ankush) — discussion
#vibecoding
3 Years of Extremely Remote Work (via majke) — discussion
#programming
Making the rav1d Video Decoder 1% Faster (by ohrv) — discussion
#c #performance #rust
Transpiler is a meaningless word (via runxiyu) — discussion
#compilers
Whippet GC notes on Guile, heuristics, and heap growth (via dustyweb) — discussion
#lisp #plt
Machinist and Machine (by jackdoe) — discussion
#philosophy
Subreply is now open source (by lucian) — discussion
#python
Root Cause Analysis: PostgreSQL MultiXact member exhaustion incidents (via jbranchaud) — discussion
#databases
Firefox Security Privacy Newsletter 2025 Q1 (via valdemar) — discussion
#browsers #security
Oodle 2.9.14 and Intel 13th/14th gen CPUs (via juri) — discussion
#assembly #debugging #hardware
By Default, Signal Doesn't Recall (via matthewfarwell) — discussion
#security #windows
libinput Preparing To Introduce A Lua-Based Plugin System For Modifying Devices/Events (via laktak) — discussion
#linux #lua
Recent disruptive changes from Setuptools (via toast) — discussion
#python
kotlin-lsp: Kotlin Language Server and plugin for Visual Studio Code (via andrewchou) — discussion
#kotlin #vscode
Using Large Language Models for Commit Message Generation: A Preliminary Study (via MatheusRich) — discussion
#vibecoding
TypeID in Lua (by pushcx) — discussion
#lua #web
Tales From Mainframe Modernization (by op) — discussion
#historical
Gradients are the new intervals (via allie) — discussion
#graphics