
Station log
Page 4 of 7. The lit span on the dial is this page.
Medium wave · 540–1600 kHz79 stations stn
STATIONS 37–48 OF 79
The Self-Hosted SaaS Replacements That Actually Work
Five SaaS tools you can replace with a $6/month VPS and open-source software — analytics, email, monitoring, git hosting, and automation.Signal vs Noise · DevOps · Developer Experience (DX)
A Strict CSP Is Easy When Your Site Is Static
A strict Content-Security-Policy is the best XSS defense most sites never ship. On a static site it's one response header and a hash — no WAF, no SaaS.Static Architecture · Astro · DevOps
Lighthouse CI Without a SaaS
Performance-monitoring SaaS sells you a wrapper around a tool you already have. GitHub Actions and Lighthouse CI fail the build on regressions for free.DevOps · Web Performance · Automation · Signal vs Noise
Stop Loading Google Fonts
Google Fonts is a tracker that happens to also serve fonts. Self-hosting is faster, more private, and a one-afternoon migration in 2026.Signal vs Noise · Web Performance · Developer Experience (DX)
Why I Deleted Google Analytics
Google Analytics is slow, GDPR-hostile, undercounted by ad blockers, and answering questions you mostly aren't asking. Here's why I removed it from every site I run, and what I use instead.Signal vs Noise · Web Performance · Developer Experience (DX)
Awesome Astro: The Opinionated Tour
The awesome-astro list is the default entry point into the Astro ecosystem. It is also half noise. Here is what to actually install — and what to skip — sorted by what survives a year of production use.Astro · Signal vs Noise · Developer Experience (DX)
We Migrated Static Signal from Next.js to Astro. Here's What Actually Changed.
Last week we published the case for picking Astro over Next.js on content sites. Then we migrated this blog. One PR, half a working day, and a Lighthouse Performance score of 100 from a real production deploy — here are the honest numbers and what surprised us.Astro · Next.js · Web Architecture · Signal vs Noise
When Astro Beats Next.js for Content Sites
Next.js is the default. It's also overkill for most content sites. Astro's island model ships less JS, builds faster, and lets you keep React where you actually need it.Static Architecture · Next.js · Web Architecture · Signal vs Noise
The Dependency-Count Audit: Every Package Is a Bet, Not a Free Tool
Most JS projects have never had their dependency list audited line by line. Doing it once — with a real method instead of vibes — usually halves the count and exposes which packages were doing nothing in the first place.Node.js · Developer Experience (DX) · Web Performance · Signal vs Noise
Cloudflare R2 vs S3 for Static Assets: The Egress Bill Is the Whole Argument
S3 is the default because it's been the default. For static assets served at scale, R2's zero-egress pricing rewrites the math — and the cases where S3 still wins are smaller than people think.Cloud Platforms · Static Architecture · Web Architecture · Signal vs Noise
The Business Case for Dumping WordPress: Static Sites and CDNs as a Line-Item Decision
Most arguments against WordPress are technical. The stronger case is financial — hosting costs, security incidents, page-speed revenue impact, and maintenance hours add up to a budget line that a static site on a CDN simply doesn't have.Wordpress · Static Architecture · Cloud Platforms · Signal vs Noise
Code Highlighting at Build Time: Shiki vs Prism and the Death of Runtime Tokenizers
Shipping a tokenizer to the browser to color code blocks made sense in 2014. It doesn't now. Build-time highlighting is faster, cheaper, and produces better-looking output — and the tradeoffs are smaller than you think.Developer Experience (DX) · Static Architecture · Web Performance · Web Architecture

