Reports of the Death of California High-Speed Rail Have Been Greatly Exaggerated
asteriskmag.com
Show HN: I built a hardware processor that runs Python
runpyxl.com
Reports of widespread power cuts in Spain and Portugal
bbc.com
Show HN: A pure WebGL image editor with filters, crop and perspective correction
github.com
Vision Transformers Need Registers
arxiv.org
Show HN: Sim Studio – Open-Source Agent Workflow GUI
github.com
Giving Software Away for Free
simonwillison.net
The Side Hustle From Hell
blog.jacobstechtavern.com
Show HN: Web-eval-agent – Let the coding agent debug itself
github.com
Activeloop (YC S18) Is Hiring VP of Engineering in Mountain View (On-Site)
careers.activeloop.ai
Uncovering the mechanics of The Games: Winter Challenge
mrwint.github.io
Show HN: Heart Rate Zones Plus – The first iOS app I ever developed
apps.apple.com
Tiny-LLM – a course of serving LLM on Apple Silicon for systems engineers
github.com
Show HN: Autarkie – Instant grammar fuzzing using Rust macros
github.com
Generating Mazes with Inductive Graphs (2017)
jelv.is
Why Momentum Works (2017)
distill.pub
Is Outbound Going to Die?
rnikhil.com
The Books of Earthsea by Ursula K. Le Guin
lars.ingebrigtsen.no
Reanimation of the original Logic Theorist, the first AI, in IPL-V
youtube.com
Show HN: I made a web-based, free alternative to Screen Studio
screenrecorder.me
AI helps unravel a cause of Alzheimer’s and identify a therapeutic candidate
today.ucsd.edu
This is awesome. I've been working on a project to make the PostgreSQL/EdgeDB/Gel protocols declarative in Rust (see https://github.com/geldata/gel-rust/blob/master/gel-pg-proto... for an example) and my approach to fuzzing has been somewhat arbitrary (you can see at the bottom).
I've used AFL but never managed to create a consistent fuzzing process using it.
This _should_ allow me to add some more extensive fuzz tests than I've currently been using, even though the grammar is binary since we're really just "parsing" and "rendering" text that happens to be [u8] rather than str.
I don't think there's been any real discussion of the Postgres message format philosophy, but it's a very regular syntax: messages are composed of primitives and lists. Lists are either length-prefixed or zero-suffixed. Everything else is just a combination of these building blocks.