Pleopods

Archives
Log in
Subscribe
July 17, 2026

Pleopods Weekly #19 — July 17, 2026

Pleopods Weekly #19 — July 17, 2026

Pleopods
Home Archive

Pleopods Weekly #19 — July 17, 2026


This Week on Lobste.rs

Trending topics: web zig rust javascript vibecoding


1. lobste.rs is now running on SQLite meta

submitted by thomas0 — 413 points (+390 this week) — 97 comments

The Lobsters community migrated from MariaDB to SQLite in production, halving their VPS costs and dropping CPU and memory usage—a reminder that the "right" database choice often depends on who's willing to do the work, not abstract best practices.

2. Lobsters Interview with mitchellh interview person

submitted by veqq — 207 points (+162 this week) — 27 comments

Hashimoto walks through his shift from distributed systems to building a GPU-accelerated terminal, and sketches out two concrete protocol additions—an n-screen API and button protocol—that could solve actual terminal problems without overhauling PTY itself.

3. Just Let Me Write Digits a11y javascript web

submitted by gendx — 147 points (+126 this week) — 35 comments

A Swiss government login system silently rejects verification codes entered in Firefox on Linux, and since the only way to contact support is through that same broken form, users hit a wall — a sharp reminder that mandatory digital identity systems have real accessibility gaps.

4. My Thoughts on the Bun Rust Rewrite javascript zig

submitted by kristoff — 132 points (+109 this week) — 35 comments

Kelley argues that Bun's switch from Zig to Rust wasn't actually about language limitations—the real issue was architectural debt and poor maintenance discipline, which a rewrite won't fix; he systematically rebuts the blog post's technical claims while noting that Zig's maintainers saw the split as a net positive anyway.

5. Rewriting Bun in Rust rust vibecoding zig

submitted by mitsuhiko — 132 points (+108 this week) — 179 comments

Bun is rewriting its core in Rust after hitting the limits of Zig: the language's manual memory management clashed too often with JavaScript's garbage collection, leaving them vulnerable to heap-use-after-free crashes and memory leaks that code review alone couldn't prevent.

6. Quadrupling code performance with a "useless" if c performance

submitted by purplesyringa — 123 points (+108 this week) — 14 comments

A single conditional guard around a register read—where the condition never changes—lets the CPU speculatively execute loop iterations in parallel by hiding a data dependency behind branch prediction, turning a latency-bound loop into a throughput-bound one and quadrupling performance in the process.

7. You paid me, a long-time Linux user, to use Windows 11 exclusively for a month: here’s how it went windows

submitted by ninakali — 139 points (+106 this week) — 51 comments

A Linux veteran crowdfunded into Windows 11 hit the expected snags—Wi-Fi 7 drivers missing from three-year-old hardware, unreliable sleep/wake cycles, sparse keyboard options—but found some things genuinely worked better.

8. An update on the scraper situation security web

submitted by fanf — 113 points (+105 this week) — 49 comments

A year in, residential proxies—malware quietly running on people's devices—have become the main tool for scraping at scale, with streaming sticks a favored infection vector; the visible AI companies aren't the problem, but whoever's bankrolling mass data theft is.

9. SQLite should have (Rust-style) editions databases

submitted by mort — 120 points (+99 this week) — 30 comments

SQLite's foreign keys are off by default and the database silently coerces wrong types—problems the author thinks editions (borrowed from Rust) could solve by letting new projects opt into stricter rules without breaking legacy apps.

10. How Our Rust-to-Zig Rewrite is Going compilers rust zig

submitted by rrampage — 109 points (+88 this week) — 38 comments

A year and a half into rewriting Roc's 300K lines of Rust into Zig, the team hit feature parity—and gained compiler capabilities like hot code loading and zero-allocation pattern matching that the old architecture couldn't support.

11. Linus Torvalds on LLM usage in kernel development linux vibecoding

submitted by thang — 117 points (+83 this week) — 98 comments

Linus makes explicit what Linux's position is: AI tools are allowed because they're technically useful, ideology doesn't override that, and maintainers should use them to reduce their workload, not expand it—full stop.

12. Jurassic Park computers in excruciating detail historical

submitted by jbauer — 100 points (+82 this week) — 12 comments

The author identifies every computer that appears on screen in Jurassic Park and uncovers what software actually ran on them — including the discovery that the hurricane animation used real meteorological data from Earthwatch, piped live to set via radio operators.

13. Closing a three-year-old issue using Rust arenas performance rust

submitted by giacomo_cavalieri — 91 points (+82 this week) — 12 comments

A developer fixed chronic performance issues by ditching reference-counted pointers for a typed arena allocator—less flexible, but with predictable memory layout and no fragmentation headaches.

14. Hannah Montana Linux v26.0 linux release

submitted by hoistbypetard — 77 points (+75 this week) — 8 comments

A joke Linux distro themed around a Disney show from 2 decades ago just hit version 26.0 — turns out there's real package management under the gag.

15. Human Emacs emacs

submitted by tusharhero — 92 points (+72 this week) — 51 comments

Emacs maintainers are threatening to fork over GNU's upcoming AI policy, specifically demanding a ban on LLM-generated code contributions rather than a case-by-case approach — the debate hinges on principle, not whether the code actually works.

16. Evan's Jujutsu Tutorial vcs

submitted by evmar — 80 points (+67 this week) — 21 comments

The author maps Jujutsu's commands and workflows against Git equivalents, then links to other guides for different learning styles—useful if you already think in terms of staging, commits, and branches.

17. The git history command deserves more attention vcs

submitted by gnyeki — 70 points (+66 this week) — 6 comments

Git's new history subcommands (fixup, reword, split) let you do jj-style rewrites on parallel branches without risk—no half-broken repos or forced migration away from git.

18. Who does Anubis actually stop? web

submitted by zk — 68 points (+62 this week) — 76 comments

The Linux kernel mailing list's new anti-bot proxy adds a speed bump for AI tools but breaks accessibility tools, RSS readers, and text browsers while costing users seconds per visit — a tradeoff that likely wastes far more human time than it prevents.

19. I Did Not Kill Stanley Lieber: How to draw (with 9front) art

submitted by pmjv — 69 points (+61 this week) — 12 comments

A guide to drawing on 9front that starts with hardware picks (ThinkPad tablets) and walks through paint(1)'s stripped-down feature set—no pressure, no layers, no undo—which turns out to map surprisingly well to how you'd actually draw on paper with a pen.

20. You should probably check on your smart appliances security web

submitted by cadey — 74 points (+60 this week) — 23 comments

Honeypot data from a reputation database reveals that 90% of scraper traffic comes from IPs unknown to existing threat lists—suggesting compromised IoT devices are being quietly enrolled in proxy networks at scale.


Pleopods is a weekly digest of the top links from Lobste.rs. Unsubscribe | Archive

Don't miss what's next. Subscribe to Pleopods:
← Newer Pleopods Weekly #20 — July 24, 2026 Older → Pleopods Weekly #18 — July 10, 2026
Powered by Buttondown, the easiest way to start and grow your newsletter.