The article already concludes coding agents have uses in areas they already do well. What specifically can be continued leading you to think should instead not be used?
I guess I don't understand how people don't see something like 20k + an engineer-month producing CCC as the actual flare being shot into the night that it is. Enough to make this penny ante shit about "hurr hurr they could've written a native app" asinine.
They took a solid crack at GCC, one of the most complex things *made by man* armed with a bunch of compute, some engineers guiding a swarm, and some engineers writing tests. Does it fail at key parts? Yes. It is a MIRACLE and a WARNING that it exists at all? YES. Do you know what you would have with an engineer-month and 20k in compute trying to write GCC from scratch in 2 weeks in 2024? A whole heck of a lot less than they got.
This notion that everything is the same just didn't make contact on 2025, and we're in 2026 now. All of software is already changing and HN is full of wanking about all the wrong stuff.
The title doesn't even seem to be intended as a shot in the night, despite that being how most of the HN took it. I.e. the author isn't saying "don't use agents because Claude Code is written in Electron" they are genuinely looking at why one would still have their agents write an Electron app over native when using coding agents.
Really truly what do we know about them based on that decision? I submit the answer is basically nothing.
Instead, we’re sort of coasting on priors and vibes about “native” tool kits being better. And that’s just catnip for people on the Internet who want to talk shit about code and don’t know what the fuck they’re talking about.
If native is a stand in for better in your mind and you conclude that they made a choice that was worse because it’s not native then therefore you can conclude that they are bad somehow. But the connective tissue there is not whatever they’re designing choice is (and of course we have no vision into the actual choices). It’s the un-investigated prior. That native is good and cross platform is bad. That’s really what people are arguing in this thread.
And the only reason we don’t see that is completely fucking ridiculous is because we are also interested in talking about how AI is bad.
So everyone gets to have two bites of the cookie and nobody gets to defend an actual argument. It’s so silly that I don’t think that we can claim that the piece is actually much more moderate and subtle than everyone is reading it to be. Because that’s kind of a dastardly position too. It allows the main argument to be advanced, and whenever it is questioned, one can retreat to claims of nuance.
Instead, let’s just say that it’s silly.
The article doesn't go as far as saying Electron is bad or judge Anthropic based on their use of it. It says Electron has downsides which are dramatically outweighed by the upsides and then shows that calculus remains true (i.e. the benefits of Electron still outweigh any of the potential downsides) even when using LLMs as coding agents. The article is not setting out to ridicule anything, it's investigating why Electron is still a good choice in the coding agent use case by looking at one such app (the Claude desktop app) written very close to home for coding agents as an example.
About the only thing the article can be said to ridicule at all is that the Claude app is slow and buggy (which is accurate IMO) but it's never saying that to imply it's impossible to solve that because it's an Electron app or that it means one should not use coding agents. The rest of the article really stands to state quite the opposite.
As the article concludes, it is a pro-Electron usage pro-coding-agent piece. I.e. that the Claude desktop app is written in Electron is NOT evidence either Claude or Electron must be bad:
> For now, Electron still makes sense. Coding agents are amazing. But the last mile of dev and the support surface area remains a real concern.
That last mile is where the author places the problems, and they had placed them there regardless whether one uses Electron or coding agents, so it's hard to take it as a hit piece for those two things.
"The state of coding agents can be summed up by this anecdote:
Claude spent $20k on an agent swarm implementing (kinda) a C-compiler in Rust, but desktop Claude is an Electron app."
We haven't made it 100 words in and we already have the core claim. In case we missed it, the author puts it in an inset later:
>So why are we still using Electron and not embracing the agent-powered, spec driven development future?
We get to the end where the author says:
"For now, Electron still makes sense. Coding agents are amazing. But the last mile of dev and the support surface area remains a real concern."
That's both true and and misleading. It's misleading because we can all agree with this sober-minded concluding statement and forget it's just based on "Electron bad, native good". The real logical sequence the author needs us to follow is:
Anthropic said code is free now. > Native code is harder than that for a cross platform runtime > Anthropic releases an app on a cross-platform runtime > code must not be free.
That is only true iff there's absolutely no other design tradeoff! Did they pick electron because robots are bad at the last mile? Maybe. It's pretty dubious, given the MANY MANY other people who made electron apps before AI could code. It's also not at all clear "native good, electron bad" is true at all. It reminds me STRONGLY of "jQuery bad / native good" which was also groundless.
I.e. yes, coding agents can't make everyone happy and do 100% of everything - but by the end the opposite of the expected point from that is reasoned. It may not be exhaustive, but that does not automatically mean the sole point is reductionist. It only takes one counterexample of reasoning to show a point invalid, so if you don't assume the goal is to make Electron and Claude actually sound bad then these points are not really problematic.
As someone who sees themselves more towards the center of the AI debate I found the article surprisingly refreshing in not trying to argue absolutes about extremes. Others who sit more towards the extremes probably see it as an attack piece (regardless of which extreme) just because it doesn't go as far as they'd like in each regard.
You can't conclude anything reliably from their choice of electron over native apps. You can't. You can ASSERT things like the author does, like "The state of coding agents can be summed up by this fact: Claude spent $20k on an agent swarm implementing (kinda) a C-compiler in Rust, but desktop Claude is an Electron app." That's a fine assertion. It's just not a fact or knowledge about any kind of design decision.
The whole argument revolves around knowing that electron is a compromise because one could just make multiple native apps without asking if "make multiple native apps" serves a design need the developers had at all! If the developers (like many others who use electron) did not declare "we want to make native apps" or have a need that caused that to become a desire, then inferring that using electron is a compromise at all is groundless. It may never have been a compromise to begin with!
"We have cheap elevators, why aren't all floor connections using them?
The state of elevators can be summed up by this fact: The OTIS Elevator Company Factory Building cost $x million to build, but it still has stairs"
The only thing this section asserts is "stairs seem to still be chosen". It's not actually asserting anything else yet, it's grabbing the attention of those who commonly assume this must mean a lot of things. It sounds exactly like something someone who would want to say Elevators and OTIS are useless bad crap would start with, but intentionally stops short of that conclusion from these to instead take things in a different direction which is still compatible with this information.
The assertions on Electron actually start later on here, and do not source from the design decisions of the Claude desktop app:
> There are downsides though. Electron apps are bloated; each runs its own Chromium engine. The minimum app size is usually a couple hundred megabytes. They are often laggy or unresponsive. They don’t integrate well with OS features. (These last two issues can be addressed by smart development and OS-specific code, but they rarely are.
These are not sourced from the design decisions of Anthropic. The first is an assertion of fact of what Electron is, a bundled instance which runs a full browser engine resulting in a large minimum app size. The next two assertions are actually not assigned to Electron itself, rather development effort. The only poorly sourced assertion here is that such apps are rarely well optimized, but if you take issue with that it does not actually impact the rest of what the article talks about.
The article then spends some time talking about why Electron is actually a common choice despite this, which eventually leads to the actual assertions about Electron's usage in the Claude app:
> But we’re still leaning on Electron. Even Anthropic, one of the leaders in AI coding tools, who keeps publishing flashy agentic coding achievements, still uses Electron in the Claude desktop app. And it’s slow, buggy, and bloated app.
There are 3 assertions here.
1. Anthropic has shown all sorts of flashy things with AI coding tools
2. The app is still using Electron
3. The app is slow, buggy, and bloated.
These assertions are not interdependent, they are just observations of the app. The article is still not arguing Electron can only be slow/buggy (though it has previously asserted it must be bloated by nature) nor is the app asserting why Anthropic has made these design choices yet. It is still following the train of thought one might be biased to from the original thought but carrying it further to perhaps unexpected conclusions.
The question in the reader's mind the article seeks to next pre-emptively answer is now stated: "So why are we still using Electron and not embracing the agent-powered, spec driven development future?". Most likely the reader has "make it a native app" as the first path, but the article already laid out 2/3 of these things can be solved with a smartly written Electron app. In either case, the article is not asserting why the Claude desktop team chose/chooses a particular design choice, it's seeking to answer why having great coding agents isn't necessarily a free answer to slowness, bugginess, and bloat in a cross platform app.
This is where the article finally makes its core argument:
> For one thing, coding agents are really good at the first 90% of dev. But that last bit – nailing down all the edge cases and continuing support once it meets the real world – remains hard, tedious, and requires plenty of agent hand-holding.
Using quotes from Anthropics implementation of the C compiler to back up this claim and then continue discussing how the benefits of a common approach over an optimised approach still exists outside of the raw code writing portion of the problem. At this point the article is still avoiding that the Claude desktop team must want a native app as a design goal, only speaking to why coding agents aren't the cure-all for the particular problem set (regardless of approach).
This is why the article concludes:
> For now, Electron still makes sense. Coding agents are amazing. But the last mile of dev and the support surface area remains a real concern.
Rather than:
> For now, it's clear coding agents must suck because Anthropic hasn't used them to come up with a more efficient alternative to the obviously poor choice of Electron or rewrite the app as separate native apps - which must obviously be their goal because coding agents are supposed to be able to write code