231–240 of 483 posts
Earlier quoted context omitted.
Couldn't this have been vibe coded into a native app that is more performant?
> vibe coded > more performant I found the problem.
Earlier quoted context omitted.
Agreed! I built a MacOS Postgres client with just Claude Code[1]. It could use some UI improvements, but it runs much better than other apps I’ve tried (specifically what it’s replacing for me: RazorSQL) and the binary is smaller than 20MB. 1: https://github.com/NeodymiumPhish/Pharos
Tauri is still a WebView wrapped in some chrome, right? That's not what I would consider "native".
Boris 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!
With your context and understanding of the coding agent's capabilities and limitations, especially Opus4.6, how do you see that going?
Boris 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!
Didn’t you say coding is a solved problem? So why are you still reaching for the lowest common denominator tech stack?
Boris 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!
As a user I would trade fewer features for a UI that doesn't jank and max out the CPU while output is streaming in. I would guess a moderate amount of performance engineering effort could solve the problem without switching stacks or a major rewrite. (edit: this applies to the mobile app as well)
Boris 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!
I keep being told by Anthropic and others than these AI coding tools make it effortless to write in new languages and port code from one language to another. This is an important lesson to watch what people do, not what they say.
Boris 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!
Didn’t you say coding is a solved problem? So why are you still reaching for the lowest common denominator tech stack?
Boris 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!
I'm glad to see this coming from a company that is so popular these days.
Thanks!
Earlier quoted context omitted.
> vibe coded > more performant I found the problem.
I mean, we both know it couldn't, but the company claims it can be done so why don't they do it?