LEXER

The tech wire, torn down to the stories that mattered.

Lexer reads the feeds, Hacker News and Reddit so you don't. Duplicate coverage collapses into one entry, stories are picked by rules you could audit, and an editor signs off on every issue before it reaches your inbox.

Free. Confirm by email. Unsubscribe in one click.

LEXER WIRE sample feed · illustrative
  1. 06:02 RSS Postgres 18 adds asynchronous I/O for sequential scans kept: lead
  2. 06:05 HN 612 Postgres 18 is out: async I/O, uuidv7(), virtual columns duplicate: dup 01
  3. 06:11 r/prog 1.4k PG18 async IO benchmarks megathread duplicate: dup 01
  4. 06:19 RSS Open-weights coding model publishes its full eval harness kept: main
  5. 06:24 r/LLaMA 880 NEW MODEL DESTROYS EVERYTHING (thread) dropped: hype
  6. 06:31 HN 344 Show HN: a terminal UI for reading Postgres query plans kept: tool
  7. 06:38 arXiv Speculative decoding without a separate draft model kept: deep
  8. 06:40 r/ML 212 [D] Speculative decoding paper discussion duplicate: dup 07
  9. 06:47 HN 96 Why I quit my startup (2019) dropped: stale
  10. 06:52 RSS Browsers move to partitioned storage by default kept: main
  11. 06:58 HN 508 Third-party iframes lose shared storage next quarter duplicate: dup 10
11 lines in 5 kept for the issue

How an issue gets made

The pipeline does the reading. A person does the judging. Every issue passes through the same five steps.

  1. Read the wire

    Publisher and engineering-blog RSS feeds, Hacker News and a handful of developer subreddits, pulled several times a day.

    everything comes in

  2. Collapse duplicates

    Articles about the same event are clustered by meaning, not by headline. Seven write-ups of one release become one entry, with the strongest source on top.

    one story, one entry

  3. Select by rules

    Ten slots across five sections. A story earns its slot with measurable signal: how many independent sources covered it, and how engineers on HN and Reddit responded.

    rules you could audit

  4. Summarize

    Each pick gets a short summary that says what changed and why it matters to someone who ships software, with a link to the original.

    what changed, why it matters

  5. Editor signs off

    A person reads the draft, fixes summaries, reorders stories and approves it. Nothing reaches your inbox unreviewed.

    a human, every issue

What lands in your inbox

Ten stories in five fixed sections, each with one line marked in red: the sentence that tells you whether to care.

Sample issue with illustrative stories. Real issues follow this exact structure.

LEXER sample issue · 10 stories

Lead

The story with the widest independent coverage.

  • 01

    Postgres 18 lands with asynchronous I/O

    Read-heavy workloads get faster sequential and bitmap scans with no config changes. If you run analytics on Postgres, this is a free speedup on upgrade.

    7 sources collapsed

Main

Covered by two or more sources, or a strong engineer response.

  • 02

    An open-weights coding model ships its eval harness

    Weights, prompts and scoring scripts are all public. You can reproduce the benchmark numbers yourself instead of trusting a chart.

    4 sources
  • 03

    Browsers converge on partitioned storage

    Third-party iframes stop sharing cookies and storage across sites. Embedded logins and widgets need testing before the change ships.

    3 sources
  • 04

    A native-speed TypeScript compiler preview

    The preview installs next to tsc and type-checks large repos much faster. Worth a trial run in CI; it is a preview, not a drop-in yet.

    5 sources
  • 05

    Retry storms behind this month's outage write-ups

    Several public postmortems trace back to synchronized retries. Jittered backoff is the boring fix that would have stopped most of them.

    2 sources

Quick hits

Single-source items that engineers clearly cared about.

  • 06

    Show HN: a one-file HTTP load tester

    No config, readable output. Good for a five-minute sanity check before a launch.

    HN
  • 07

    What's your on-call ritual?

    A long, practical Reddit thread. The runbook-first replies are the useful ones.

    Reddit
  • 08

    curl retires an old TLS backend

    Builds that pin it will need a switch. Check your Dockerfiles if you compile curl yourself.

    RSS

Deep dive

A paper or long read worth a proper sit-down.

  • 09

    Speculative decoding without a draft model

    A clear walk-through of self-speculation, with code. Explains why long outputs get cheaper, not just faster.

    arXiv

Tool

One new release or open-source project.

  • 10

    A terminal UI for Postgres query plans

    Turns EXPLAIN ANALYZE into a navigable tree. Pairs well with this issue's lead story.

    HN

What you won't get

  • The same launch, covered six timesOne story, one entry, best source first.
  • Hype threads and engagement baitStories earn a slot with signal, not volume.
  • An unreviewed robot digestAn editor approves every issue.
  • A hard-to-leave mailing listChange preferences or unsubscribe in one click.

Tear off your copy.

The stories that mattered, in one short read.