LinkedIn is searching your browser extensions

Google releases Gemma 4 open models

Decisions that eroded trust in Azure – by a former Azure Core engineer

Qwen3.6-Plus: Towards real world agents

Tailscale's new macOS home

Cursor 3

Inside Nepal's Fake Rescue Racket

Good ideas do not need lots of lies in order to gain public acceptance (2008)

Artemis II's toilet is a moon mission milestone

OpenAI Acquires TBPN

Show HN: European alternatives to Google, Apple, Dropbox and 120 US apps

<a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;George_H._Goble" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;George_H._Goble</a>

George Goble has died

C89cc.sh – standalone C89/ELF64 compiler in pure portable shell

Significant progress made on Xbox 360 recompilation

JSON Canvas Spec (2024)

Proton Meet Isn't What They Told You It Was

Show HN: Apfel – The free AI already on your Mac

ESP32-S31: 320MHz 2C RV32IMAFCP+CLIC, 512KB SRAM, GbE, 802.11ax, 61 GPIO

NHS staff refusing to use FDP over Palantir ethical concerns

A developer&#x27;s machine accumulates tools fast. A Rust CLI you compiled last year, a Python formatter installed via `uv`, a language server pulled from npm, a terminal emulator from a curl script, a Go binary built from source. Each came from a different package manager, each with its own install incantation you half-remember.<p>I wanted a way to declare what I need without adopting a complex system like Nix or Ansible just for a single laptop. The result was a plain old Makefile.<p>I wrote a short post on using Make (along with a tiny bash script and fzf) to create a searchable, single-command registry for all your local dev tools. It’s not a new framework or a heavy tool—just a simple way to organize the package managers we already use.<p>If you&#x27;re tired of losing track of your local environment, you might find it useful.

Show HN: Home Maker: Declare Your Dev Tools in a Makefile