One too many words on AT&T's $2,000 Korn shell and other Usenet topics (by gnyeki) — discussion

#hardware #historical #unix

State of Elixir 2025 - Community Survey Results (via kamila) — discussion

#elixir

Commoning open-source versus growth-hacking open-source (via geekingfrog) — discussion

#culture

ASK: What are you doing this week? (by caius)

#ask #programming

Migrating burningboard.net Mastodon instance to a Multi-Jail FreeBSD Setup (via 0mp) — discussion

#freebsd #web

potential security breach in syncthing-fork (via laktak) — discussion

#android #security

Adding unpack syntax to RCL (by ruuda) — discussion

#plt

From Azure Functions to FreeBSD (via wezm) — discussion

#freebsd

IDEsaster: A Novel Vulnerability Class in AI IDEs (via sjamaan) — discussion

#editors #security #vibecoding

Desperately seeking squircles (2018) (via fanf) — discussion

#design #math

An Attempt at a Compelling Articulation of Forth's Practical Strengths and Eternal Usefulness (by LenFalken) — discussion

#concatenative #programming

Pulldash: Fast, filterable GitHub PR review. Entirely client-side (by kylecarbs) — discussion

#nodejs #web

Measuring Agents In Production (survey paper) (via tlarkworthy) — discussion

#ai

Why the Sanitizer API is just `setHTML()` (by freddyb) — discussion

#browsers #security #web

Estimates are difficult for developers and product owners (by GLaDER) — discussion

#practices

Defeating Prompt Injections by Design (via viega) — discussion

#ai #security

F35 Fighter Jet’s C++ Coding Standards (via azhenley) — discussion

#c++ #pdf

The Gerrit code review iceberg (via FedericoSchonborn) — discussion

#osdev

KOllector - Publishing KOReader Highlights (by stonecharioteer) — discussion

#python #show

It Is Worth It To Optimize Images For Your Site (via rbr) — discussion

#web