Pleopods Weekly #30 — October 2, 2026

This Week on Lobste.rs

Trending topics: vibecoding ai linux android rust

1. “They had no concept of a duty of care to their users.” vim

submitted by raymii — 186 points (+176 this week) — 70 comments

NeoVim silently deleted vim's persistent undo files without migrating them, then dismissed the feature as unstable — a failure that's less about the bug and more about how the project handled user data loss.

2. If we do not stop to help each other, what do we become? culture

submitted by j11g — 171 points (+140 this week) — 20 comments

A soldier in an active combat zone relied on Stack Overflow's community to get through college assignments—and the piece argues that swapping human helpers for AI that answers but doesn't engage loses something crucial we haven't fully reckoned with yet.

3. CoW — a stacking window manager for Wayland linux

submitted by hawski — 138 points (+132 this week) — 17 comments

A Wayland window manager that recreates 90s aesthetics (FVWM/MWM style) while keeping modern configurability via IPC and a built-in scripting language; uses server-side decorations and rule-based window placement.

4. Bill Gates tries to install Movie Maker windows

submitted by nrposner — 144 points (+129 this week) — 28 comments

Bill Gates's 2003 complaint about Movie Maker is a masterclass in cascading UX failures: confusing search, mysterious 17MB "critical" patches, mandatory reboots, unhelpful dialogs, and an Add/Remove Programs list polluted with test packages—and the follow-up emails show no one actually owned fixing it.

5. Yes, no AI is now a feature practices

submitted by johnolinda — 127 points (+122 this week) — 31 comments

LibreOffice's five demands for trustworthy AI—user control, no sneaky data transmission, no telemetry, no vendor lock-in, open formats—rule out every implementation shipping today, which is a harder stance than just saying AI is bad, and makes sense from an organization that serves schools and hospitals instead of justifying subscriptions.

6. What Would A Serious AI Product Look Like? a11y design vibecoding

submitted by Corbin — 105 points (+95 this week) — 16 comments

Glyph points out that AI products acknowledge hallucinations but design around verification—no way to mark claims you've fact-checked, no dated sources, no audit trail—making it easier to trust than to verify.

7. Goodbye Google ai person

submitted by classichasclass — 101 points (+94 this week) — 27 comments

Robert O'Callahan, creator of the rr debugger and longtime Firefox engineer, has left Google — his post doesn't say what's next, but his track record in omniscient debugging and browser internals suggests whatever he's working on now is a deliberate departure from infrastructure work.

8. Breaking Up with Google Play: Why Conversations Is Now Free android

submitted by tusharhero — 163 points (+92 this week) — 20 comments

After 12 years selling Conversations on the Play Store, Gultsch is moving it to F-Droid as free software now that grant funding makes Google's cut and review delays (currently 14 days for security updates) economically unnecessary.

9. One month without AI ai vibecoding

submitted by Jackevansevo — 96 points (+86 this week) — 13 comments

A month off AI coding tools forced the author to confront an uncomfortable truth: they'd become a code reviewer trapped in pull requests they didn't fully grasp, no longer shipping features or writing anything themselves. Speed without understanding turns out to be its own kind of slowdown.

10. IANA's email about why example.com changed networking web

submitted by videah — 105 points (+82 this week) — 38 comments

IANA stripped example.com down to a static base page and optional JS, cutting bandwidth for the bots that make up most traffic. The VP also clarifies the domain isn't meant for uptime monitoring, despite how often engineers treat it that way.

11. Leaving them behind vibecoding

submitted by diktomat — 75 points (+74 this week) — 22 comments

A web developer is drawing a hard line: no AI in his work, full stop. He's also stepping back from peers who've embraced it, arguing the industry has shifted from craft to extracting labor at scale—and he wants no part of it.

12. postmarketOS rebrands as Nura linux

submitted by lobo — 84 points (+73 this week) — 15 comments

After 18 months of deliberation, postmarketOS rebrands to Nura, named after ancient Sardinian stone structures. The new name is shorter and easier to trademark, sidestepping the pronunciation and spelling headaches that plagued the original.

13. When did Google get so weird? ai

submitted by dimonomid — 73 points (+72 this week) — 13 comments

Google's AI overviews are now confidently misinterpreting queries—the author searched for a 2010s basketball meme and got relationship counseling instead.

14. How to speed up the Rust compiler in September 2026 compilers rust

submitted by patchunwrap — 71 points (+69 this week) — 5 comments

Two months of focused compiler tuning—borrow checker, trait solver, dataflow analysis—yielded a 4.57% mean speedup across 629 benchmarks, with most wins coming from unglamorous fixes like cutting fixpoint iterations from 1.5M to 90K on large functions.

15. What makes Lisp difficult to read? plt

submitted by veqq — 82 points (+64 this week) — 59 comments

The claim isn't that Lisp's syntax is hard — it's that the uniform structure makes it harder to spot mistakes and patterns than languages where different constructs look different, and that this gap widens the more code you read at once.

16. Lobsters: Rename vibecoding to llms (Greasemonkey script) meta vibecoding

submitted by joshka — 75 points (+63 this week) — 27 comments

A user script replaces "vibecoding" with "llms" across Lobsters—enough people have installed it that the joke suggests the original term might actually be making conversations harder to follow.

17. F-Droid 2.0 android

submitted by dimonomid — 96 points (+59 this week) — 7 comments

F-Droid 2.0 rebuilt itself in Kotlin Compose and finally fixed the friction points that made it feel sluggish next to Google Play—smarter filtering (breaking games into 17 genres), better CJK search, and an installer that uses Android's new DMA APIs to speed up app installation without compromising the no-tracking model.

18. SourceHut account takeover via build logs (XSS in ansi2html.py) security

submitted by winter — 95 points (+58 this week) — 18 comments

ansi2html's conversion of ANSI escape codes didn't properly sanitize OSC 8 hyperlink sequences, letting attackers inject arbitrary HTML into build logs that are public and pre-auth—if an admin viewed a malicious log, an attacker could steal CSRF tokens and potentially take over their account.

19. Pining for Arc Downcasting in Rust rust

submitted by polywolf — 63 points (+58 this week) — 13 comments

Arc can't downcast to Arc<T> for inner types the way owned values can pattern-match down, because Arc needs the original pointer to safely manage refcounts — but you can build a self-referential struct using raw pointers to get the "owned pointer to a nested field" you actually need.

20. What About Rails? ruby vibecoding

submitted by nick4 — 62 points (+57 this week) — 28 comments

DHH announced at Rails World that he's moving away from Rails for his own projects, dropping his Ruby work to 3%, and predicting hand-written code will be economically dead by year-end — messaging that left the attending developers without a clear picture of where Rails itself is headed.

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