Pleopods

Archives
Log in
Subscribe
April 10, 2026

Pleopods Weekly #6 — April 10, 2026

Pleopods Weekly #6 — April 10, 2026

Pleopods
Home Archive

Pleopods Weekly #6 — April 10, 2026


This Week on Lobste.rs

Trending topics: security programming vibecoding linux hardware


1. The Future of Everything is Lies, I Guess ai

submitted by orib — 157 points (+132 this week) — 29 comments

A working engineer who watched LLMs get cheaper at 2019 spells out why they're confabulation machines dressed in autocomplete — and why that matters more than whether they're "intelligent."

2. The nvim-treesitter repository was archived editors programming vim

submitted by rwdf — 142 points (+128 this week) — 102 comments

The popular nvim-treesitter plugin was archived in April 2026 after its maintainer folded the functionality into Neovim core, forcing users to either migrate their configs or stay on a frozen version.

3. Little Snitch for Linux linux release security

submitted by ehamberg — 128 points (+125 this week) — 16 comments

Objective Development released a Linux network monitor using eBPF that revealed Ubuntu's baseline sends ~9 processes home versus macOS's 100+, with most apps behaving identically across platforms except LibreOffice, which stays completely quiet on Linux.

4. Porting Mac OS X to the Nintendo Wii hardware mac osdev

submitted by calvin — 125 points (+121 this week) — 5 comments

Someone got macOS 10.0 running on a Nintendo Wii by writing a custom bootloader and patching the kernel—and when the system crashed, they rigged the Wii's front-panel LEDs to flash error codes since normal logging was offline.

5. The Downfall and Enshittification of Microsoft in 2026 linux mac windows

submitted by Caio — 110 points (+109 this week) — 41 comments

The author walks through a believable (if speculative) collapse scenario: what happens when Microsoft's aggressive AI monetization, product cannibalization, and regulatory heat compound into a death spiral? Plausible failure modes, even if the timing and odds remain entirely uncertain.

6. The Free Market Lie: Why Switzerland Has 25 Gbit Internet and America Doesn't networking

submitted by vbernat — 107 points (+103 this week) — 64 comments

Switzerland treats fiber as neutral, shared infrastructure that any ISP can plug into; the US and Germany both ended up with monopolies or wasteful duplication, but for opposite regulatory reasons—and the article argues this matters more than whether you call it "free market" or "regulated."

7. A Cryptography Engineer’s Perspective on Quantum Computing Timelines cryptography security

submitted by fkooman — 98 points (+97 this week) — 21 comments

A cryptographer's timeline for quantum threats just collapsed from "distant future" to "33 months" after Google and Oratomic's new estimates for breaking 256-bit elliptic curves — and the math gets darker when you realize even a tiny failure probability becomes unacceptable at scale.

8. Every dependency you add is a supply chain attack waiting to happen programming

submitted by benhoyt — 93 points (+91 this week) — 53 comments

The real risk isn't adding a dependency — it's auto-updating one without review, which is how XZ, Trivy, and LiteLLM got compromised, and turning off Dependabot might actually reduce your attack surface more than auditing does.

9. Eight years of wanting, three months of building with AI vibecoding

submitted by cgrinds — 90 points (+84 this week) — 16 comments

Eight years of thinking, three months to build with AI agents, and a unflinching look at which parts actually worked versus which ones turned into unmaintainable mess.

10. Where can I find the old internet? ask culture

submitted by kghose — 87 points (+82 this week) — 61 comments

The OP is chasing that feeling of stumbling onto lovingly-maintained corners of the web built by people hyperfocusing on obscure things for no money — and the thread surfaces what still exists (Usenet via Eternal September, MUDs, small-web search engines like Marginalia and Kagi's lens) alongside the harder truth that you've probably changed more than the internet has.

11. The Last Quiet Thing hardware

submitted by Aks — 82 points (+78 this week) — 46 comments

The author argues that smart devices have become parasitic rather than useful—constantly demanding attention and updates while "wellness" apps monetize the exhaustion they partly caused, and that your fatigue from managing them all isn't a personal failing but a reasonable response to objects designed to never let you rest.

12. Claude Code Found a Linux Vulnerability Hidden for 23 Years security vibecoding

submitted by mtlynch — 81 points (+78 this week) — 25 comments

Claude found a remotely exploitable heap buffer overflow in the Linux NFS driver that had gone unpatched since 2003 by simply asking it to hunt for vulnerabilities — and has reportedly discovered hundreds more, with the actual bottleneck now being manual human validation rather than finding them.

13. The Seed Beneath the Snow practices

submitted by krig — 78 points (+77 this week) — 5 comments

The formal org chart is theater; the real software team runs on unmapped relationships and favors, which turns out to have deep historical roots in mutual aid and anarchist organizing—and fighting to protect those backchannels might matter more than optimizing them away.

14. Slap: Functional Concatenative Language... with a Borrow Checker? compilers concatenative graphics plt

submitted by surprisetalk — 91 points (+76 this week) — 14 comments

Concatenative stack language with Rust-style linear types and a 2,000-line C implementation — the author's betting that forcing you to reason about memory and stack effects explicitly beats hidden complexity, and backs it up with working Game of Life and snake demos.

15. Stamp It! All Programs Must Report Their Version go nix

submitted by stapelberg — 97 points (+74 this week) — 40 comments

Stapelberg argues that software version reporting is absurdly broken compared to physical appliances — most programs can't tell you what's actually running in production without detective work. He shows how three simple practices (embedding build info, threading it through your system, and exposing it to users) turned hours of guessing into straightforward incident response.

16. Adobe wrote to my hosts file design

submitted by ohrv — 77 points (+68 this week) — 20 comments

Adobe's installer wrote entries directly to the hosts file to block domains, persisting after uninstall — the kind of thing that would tank a smaller company's reputation but apparently just gets a shrug from a $20B vendor.

17. Someone at BrowserStack is Leaking Users' Email Address privacy

submitted by deevus — 81 points (+65 this week) — 19 comments

BrowserStack secretly shared customer emails with Apollo.io through a data-sharing program, then Apollo claimed the emails were algorithmically derived until BrowserStack contradicted that story—but neither company will explain what actually happened or why.

18. Assessing Claude Mythos Preview’s cybersecurity capabilities security vibecoding

submitted by equeue — 69 points (+64 this week) — 33 comments

Anthropic's new Mythos Preview autonomously discovers and chains zero-days across OSes and browsers — so effective that the team is limiting early access to critical partners while defensive tools catch up.

19. If you thought the speed of writing code was your problem - you have bigger problems practices

submitted by drmorr — 64 points (+62 this week) — 18 comments

The real bottleneck in most organizations isn't how fast developers write code — it's everything that happens after: code review backlogs, CI/CD delays, unclear requirements, and deployment queues that turn shipping into a multi-month slog, so bolting on AI coding assistants just creates unreviewed PRs piling up faster than reviewers can handle them.

20. What are your programming "hunches" you haven't yet investigated? ask programming

submitted by WilhelmVonWeiner — 70 points (+59 this week) — 108 comments

A collection of half-baked ideas that never shipped, mostly because the tradeoffs aren't actually worth it—x32 ABI could halve memory overhead but nobody ships it, and designing GUIs around accessibility first sounds better until you hit real constraints.


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 #7 — April 17, 2026 Older → Pleopods Weekly #5 — April 3, 2026
Powered by Buttondown, the easiest way to start and grow your newsletter.