You can contribute to KDE with non-C++ code (via raymii) — discussion

#c++

Against XMPP+OMEMO (via unlobito) — discussion

#cryptography

The difference between undefined behavior and ill-formed C++ programs (via dureuill) — discussion

#c #c++

Invest in Interfaces (via cnln) — discussion

#design #hardware

Inkbase: Programmable Ink (via strongoose) — discussion

#design #programming #visualization

arrival-time: Simple and powerful progress time estimation (ETA) (by vitonsky) — discussion

#javascript

Perfect NAS Solution (by vermaden) — discussion

#freebsd #hardware

Multiplier v2: Code indexer specialized for C/C++ (via azeemba) — discussion

#c++ #compilers #security

What Would It Take to Recreate Bell Labs? (via robey) — discussion

#culture #historical

Reverse engineering the 59-pound printer onboard the Space Shuttle (via jmillikin) — discussion

#hardware #reversing

Clang vs. Clang (via squadette) — discussion

#compilers #cryptography #security

Back-dating Git commits based on file modification dates (via pushcx) — discussion

#vcs #web

Versioning as Communication (via EvanHahn) — discussion

#practices

Go debug your core dumps somewhere else (by yshui) — discussion

#debugging #linux

A Knownbits Abstract Domain for the Toy Optimizer, Correctly (via Corbin) — discussion

#compilers #formalmethods #plt

Towards userspaceification of POSIX - part I: signal handling and IO - Redox - Your Next(Gen) OS (via rslabbert) — discussion

#osdev #rust

Clinic Publishes Update to Security Researcher’s Guide to Legal Risk (via pushcx) — discussion

#law #pdf #security

Primitive Recursive Functions For A Working Programmer (via antonz) — discussion

#programming

"We ran out of columns" - The best, worst codebase (via 3digitdev) — discussion

#programming

Racket meet-up: Saturday, 3 August, 2024 at 18:00 UTC (by spdegabrielle) — discussion

#lisp