Debate Ignites Over 'Native' Dev Experience
A popular engineering blog post argues that the developer tool industry has "lost native," pointing to AI assistants like Claude shipping as Electron apps. The debate on Hacker News highlights growing developer frustration with bloated, non-native tools, suggesting that performance and a lightweight feel are key differentiators for new dev-focused products.
The original post, "The Fall of Native," was penned by Nikita Prokopov, creator of the Fira Code font. He argues that native has lost its edge because OS vendors provide terrible, inconsistent APIs, making it a hostile environment for developers long before AI code generation became a factor. On a Hacker News thread discussing the topic, a team member from Anthropic, Boris Cherny, explained the choice for Claude. He noted that some engineers on the team had previously worked on Electron, and the framework guarantees that features and the user experience are consistent between their web and desktop products. The core of developer frustration stems from the resource-heavy nature of Electron apps, which bundle a full Chromium browser. This can lead to high memory consumption, larger application sizes often starting around 120MB, and noticeable battery drain on laptops, a common complaint for widely used tools like Slack, Microsoft Teams, and VS Code. The business trade-off, however, is clear: speed. Electron allows companies to write code once and deploy it across Windows, macOS, and Linux. This avoids the significant cost and time required to maintain three separate codebases and hire specialized native developers for each platform, prioritizing faster iteration and market entry. In response to this bloat, a new generation of frameworks is emerging. Tauri, for instance, aims for smaller, more secure, and performant apps by using the operating system's native WebView instead of bundling Chromium. Google's Flutter has also expanded from mobile to desktop, using its own rendering engine to ensure UI consistency. Meanwhile, established players are also betting on a native-first approach for new developer tools. JetBrains, for example, built its next-generation IDE, Fleet, on the JVM and Kotlin. It features a distributed architecture that separates the lightweight UI from the powerful IntelliJ code-processing engine to maximize performance.
