Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #17960

R

Ryan Rasti

Personal blog · ryanrasti.com/blogprogrammingsystems

Ryan Rasti's personal blog at ryanrasti.com covers programming and systems. Since 2025, 4 different Hacker News readers have linked it 5 times, most often “Why Nix Will Win (and What's Stopping It)”. It is still writing: the last post was on 2026-01-29, and you can follow it by feed.

Visit the blog
5mentions?
4HN people?
2025–2025first – last linked?

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

HN commenters link this blog's posts on choosing Elixir Phoenix over other web frameworks and on using Nix to reduce SaaS lock-in by treating cloud providers as commodities. Comments engage with the Elixir and Nix ideas.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Technical insights on distributed systems, pragmatic engineering, and building from zero to one.

Most-linked posts?

  1. Why Nix Will Win (and What's Stopping It)
    3 people · 3 mentions · first linked 2025-10-09
  2. Building with Elixir for Three Years: A Production Retrospective
    2 people · 2 mentions · first linked 2025-10-15

What Hacker News says?

  1. I share the OP's enthusiasm for Elixir, but as the CTO of a startup that ran it for three years in production, our experience was a mixed bag as the codebase grew. The core promises of the BEAM (concurrency, fault tolerance) absolutely held up. Libraries like Ecto and Oban are world-class, remote `iex` is a lifesaver in prod, and the talent pool is exceptional. However, developer experience (DX) was our biggest bott…

    Comment linking /blog/elixir-three-years-production/

    on “Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js”
  2. Submitted Why Nix Will Win (and What's Stopping It) as a story · 12 points

    HN discussion
  3. The fundamental SaaS lock-in comes from bundling two things: 1. A declarative, stable interface 2. An expert support/ops team I think the path forward is to unbundle them. We're already solving #1. Nix has the best potential to become that declarative & stable layer, letting us reach the goal of treating cloud providers as the simple commodities they should be (I wrote about this approach here: https://ryanrasti.com…

    Comment linking /blog/why-nix-will-win/

    on “The Great SaaS Gaslight”
  4. Submitted Building with Elixir for Three Years: A Production Retrospective as a story · 2 points

    HN discussion
  5. Submitted Why Nix Will Win (and What's Stopping It): A 3-Year Production Story as a story · 2 points

    HN discussion

Search all of HN for ryanrasti.com