March 3, 2026
Slop Wars: Native vs Electron
Claude is an Electron App because we've lost native
App wars: native purists fume, Linux fans cheer
TLDR: Claude’s desktop app uses Electron, and the article argues native apps no longer offer clear benefits. Comments split between Linux fans grateful for cross‑platform support, Mac users roasting Apple’s “native” apps, and one camp blaming developer laziness while others say results matter more than tools.
Why is Claude a desktop app built with Electron—basically a web app in a box—instead of “native”? After Drew Breunig’s question, the follow‑up take said the quiet part out loud: native has nothing to offer. The rant hits hard: operating systems make native development miserable, design “guidelines” are vibes, and performance isn’t a given—bad choices make slow apps on any platform. The punchline: rewriting your chat app in fancy native tools won’t fix company slop; lack of care will. Cue screenshots of Apple’s traffic lights and corner radiuses, and links about UIs degrading over time. Ouch, but relatable.
The comments went feral. Linux folks cheered—“Electron means it actually works on Linux,” crowed one—while Mac die‑hards admitted even Apple’s own “native” Settings and Passwords feel broken. Old‑school coders rolled in hot: “some developers are lazy, that is all,” snapped one, roasting JavaScript kids and reminiscing about text‑only interfaces. Others begged for pragmatism: the result matters more than the medium. A doomer optimist wondered if the AI hardware crunch might force leaner, efficient apps again. Jokes flew about “Liquid Glass” aesthetics, buttons with no borders, and corner radius by vibes. Verdict: everyone’s mad, nobody agrees, and Electron stays.
Key Points
- •The article argues native platforms no longer offer compelling advantages over web-based frameworks like Electron.
- •It claims native APIs are difficult to use and OS vendors have made native development less attractive, contributing to Electron’s rise.
- •The piece asserts modern native UI consistency has degraded, citing Apple design changes as an example.
- •It contends deeper OS integration offers limited practical benefits due to scarce interoperable formats and services moving to the web.
- •On performance, the article states platform choice isn’t determinative; speed depends on developer choices, citing Slack’s large payload as example.