Standing on the shoulders of giants: Colm on constant work (2023) (via bitfield) — discussion

#distributed

Name Collision of the Year: Vector (via tomhukins) — discussion

#databases #math

Case Study — Using a JavaScript component inside a Haskell application (via Hecate) — discussion

#haskell #javascript

16GB Raspberry Pi 5 on sale now at $120 (via pta2002) — discussion

#hardware

Ephemerality in User Interfaces (via xiaq) — discussion

#design #web

Journey of a C kernel engineer starting a Rust driver project (via PuercoPop) — discussion

#linux #rust #video

Things To Do For the New oils.pub Domain (by andyc) — discussion

#programming #unix

Renderling - Year in Review - 2024 (by schell) — discussion

#graphics #rust

Go is a Well-Designed Language, Actually (via ucirello) — discussion

#go

No-op compiler benchmarking (via evmar) — discussion

#performance #plt

Why Go Should Sometimes Be a No-Go (via Teckla) — discussion

#go

Arch Linux User Repository Requires Packages To Support x86_64: No ARM-Only Software (via laktak) — discussion

#linux

broccoli: A robust message queue system for Rust applications, designed as a Rust alternative to Celery (by densumesh) — discussion

#distributed #release #rust #scaling

Some Programming Language Ideas (via carlana) — discussion

#plt

Why developers dislike linters? (by raisingmonk) — discussion

#programming

De-smarting the Marshall Uxbridge (by tomscii) — discussion

#hardware

if got, want: A Simple Way to Write Better Go Tests (via telemachus) — discussion

#go #testing

Learning Pyxel: Moving Sprites with the Mouse (by athoune) — discussion

#games #python

C++26: a placeholder with no name (via raymii) — discussion

#c++

Bringing SerenityOS to real hardware, one driver at a time (via raymii) — discussion

#c++ #osdev