> Electron apps are bloated; each runs its own Chromium engine. The minimum app size is usually a couple hundred megabytes. I only see these complaints on HN. Real users don't have this complaint. What kind of low-end machines are you running, that Chromium engine is too heavy for you? > They are often laggy or unresponsive. That's not due to Electron. > They don’t integrate well with OS features. If it is good enoug…
Why is Claude an Electron app?
161–170 of 483 posts
Re: Why is Claude an Electron app?
#162Because code isn't free. I can see it in my team. We've all been using Claude a lot for the last 6 months. It's hard to measure the impact, but I can tell our systems are as buggy as ever. AI isn't a silver bullet.
I love the fact that we just got a model really capable of doing sustained coding (let me check my notes here...) 3 months ago, with a significant bump 15 days ago. And now the comments are "If it is so great why isn't everything already written from scratch with it?"
Of course the answer is all the things that aren't free, refinement, testing, bug fixes, etc, like the parent post and the article suggested.
Re: Why is Claude an Electron app?
#163> Electron apps are bloated; each runs its own Chromium engine. The minimum app size is usually a couple hundred megabytes. I only see these complaints on HN. Real users don't have this complaint. What kind of low-end machines are you running, that Chromium engine is too heavy for you? > They are often laggy or unresponsive. That's not due to Electron. > They don’t integrate well with OS features. If it is good enoug…
Not everyone is running the latest and greatest hardware, very few actually have the money for that. If you're running hardware from before this decade, or especially the early 2010s, the difference between an Electron app and a native app is unbelievably stark. Electron will often bring the device to its knees.
Re: Why is Claude an Electron app?
#164Earlier quoted context omitted.
And after 12 months, most probably no one from your team will understand what the result of half of those bugs is. When devs outsource their thinking to AI, they lose the mental map, and without it, control over the entire system.
I find this such a weird stance to take. Every system I work on and bug I fix has broad sets of code that I didn't write in it. Often I didn't write any of the code I am debugging. You have to be able to build a mental map as you go even without ai.
In sufficiently complicated systems, the 10xer who knows nothing about the edge cases of state could do a lot more damage than an okay developer who knows all the gotchas. That's why someone departing a project is such a huge blow.
Re: Why is Claude an Electron app?
#165> Electron apps are bloated; each runs its own Chromium engine. The minimum app size is usually a couple hundred megabytes. I only see these complaints on HN. Real users don't have this complaint. What kind of low-end machines are you running, that Chromium engine is too heavy for you? > They are often laggy or unresponsive. That's not due to Electron. > They don’t integrate well with OS features. If it is good enoug…
This is particularly pertinent on bulk-purchased corporate and education machines which are loaded down with mandated spyware and antivirus garbage and often ship with CPUs that lag many years behind, and in the case of laptops might even have dog slow eMMC storage which makes the inevitable virtual memory paging miserable.
Re: Why is Claude an Electron app?
#166Re: Why is Claude an Electron app?
#167Re: Why is Claude an Electron app?
#168Boris from the Claude Code team here. Some of the engineers working on the app worked on Electron back in the day, so preferred building non-natively. It’s also a nice way to share code so we’re guaranteed that features across web and desktop have the same look and feel. Finally, Claude is great at it. That said, engineering is all about tradeoffs and this may change in the future!
if that's the case, why don't you just ask it to "make it not shit"?
Re: Why is Claude an Electron app?
#169Earlier quoted context omitted.
My guy if you can’t see the problem with a $300B SF company that of course claims to #HireTheBest having a dumpy UX due to their technical choices I don’t really know what to tell you. Same goes for these companies having npm as an out-of-the-box dependency for their default CLI tools. I’m going to assume anyone who thinks that every user’s machine is powerful enough to run electron apps, or even support bloated deps…
Presumably these competent people could look at electron, think about building their own cross-platform application on top of chromium and conclude that this free as in code and beer tool fit their needs. Should they have re-written Chromium too?
Maybe their dog food isn't as tasty as they want you to believe.
Re: Why is Claude an Electron app?
#170Boris from the Claude Code team here. Some of the engineers working on the app worked on Electron back in the day, so preferred building non-natively. It’s also a nice way to share code so we’re guaranteed that features across web and desktop have the same look and feel. Finally, Claude is great at it. That said, engineering is all about tradeoffs and this may change in the future!