A guide to local coding models
aiforswes.com
Programming languages used for music
timthompson.com
Deliberate Internet Shutdowns
schneier.com
The ancient monuments saluting the winter solstice
bbc.com
Build Android apps using Rust and Iced
github.com
I announced my divorce on Instagram and then AI impersonated me
eiratansey.com
Webb observes exoplanet that may have an exotic helium and carbon atmosphere
science.nasa.gov
How I protect my Forgejo instance from AI web crawlers
her.esy.fun
Show HN: Books mentioned on Hacker News in 2025
hackernews-readings-613604506318.us-west1.run.app
Disney Imagineering Debuts Next-Generation Robotic Character, Olaf
disneyparksblog.com
Functional Flocking Quadtree in ClojureScript
lbjgruppen.com
ONNX Runtime and CoreML May Silently Convert Your Model to FP16
ym2132.github.io
Making the most of bit arrays in Gleam
gearsco.de
CO2 batteries that store grid energy take off globally
spectrum.ieee.org
More on whether useful quantum computing is “imminent”
scottaaronson.blog
QBasic64 Phoenix 4.3.0 Released
qb64phoenix.com
Show HN: Rust/WASM lighting data toolkit – parses legacy formats, generates SVGs
eulumdat.icu
Single-Pass Huffman Coding
doisinkidney.com
Rue: Higher level than Rust, lower level than Go
rue-lang.dev
Engineering dogmas it's time to retire
newsletter.manager.dev
Looks quite interesting, but at the same time I already see me having to look-up the specification too much. What I would like to understand better are other ways of accomplishing bit array matching and also performance/stability aspects - especially when it comes to the Erlang parts.