61–70 of 324 posts
Edit: yes, with WSL2 I believe in both cases.
I would have assumed almost everyone would get a Mac/Linux computer to use coding agents because Unix is their "native" platform. It's Bash tool calls all the way down.
Does anyone know a source for reliable data on what coding agent apps devs are using? How many are using Code Claude CLI vs Claude Desktop, etc?
Earlier quoted context omitted.
They vibecoded it, and admitted as much. Once it was able to self-vibecode, that's all they did. That's why it's written in React and uses gigabytes of RAM as a chat client.
You say that as if somehow the trend for cross platform desktop apps to be ridiculously bloated bundles of browser overlays is new? What major cross platform app isn't based on Electron or Tauri? Slack, Discord, VS Code, Teams, Notion...
Earlier quoted context omitted.
If everything is in the cloud and you are just prompting agents to code for you, what exactly is “a developer machine”?
I'm obviously not just prompting agents for everything. What are you on about? Why would I build my little web-apps and backends in the cloud when I can run things faster locally?
> Why would I build my little web-apps and backends in the cloud when I can run things faster locally?
Earlier quoted context omitted.
They vibecoded it, and admitted as much. Once it was able to self-vibecode, that's all they did. That's why it's written in React and uses gigabytes of RAM as a chat client.
You say that as if somehow the trend for cross platform desktop apps to be ridiculously bloated bundles of browser overlays is new? What major cross platform app isn't based on Electron or Tauri? Slack, Discord, VS Code, Teams, Notion...
It seems like the VM is a core part of how you use the application.
Earlier quoted context omitted.
Many people will say it’s because of the slop. I think it’s because they have no product vision. The roadmap is pretty much a random walk, which combined with the velocity of agentic coding is like digging a moat with atomic bombs.
I find this analogy particularly humorous, as atomic bombs do not make for good excavators
The VM itself is for Claude Cowork which does all work within the VM sandbox. That doesn't help answer why they spin it up immediately and don't have a way to disable it though. Just the "why it exists" question.
If you're not going to give Claude access to anything on your machine, why are you using Desktop instead of web chat? (Real question, I don't use these much!) If you are, obviously you need the VM.
I use Claude Code CLI myself (inside a VM, to isolate it from the host) for >90% of my needs. For the remaining fraction - email scours, cloud drive searches, other third-party connections - the desktop application is surprisingly decent. I don't even have more than half a dozen connectors enabled. In the VM I have separate, personally managed access tokens available for various third-party services. Wouldn't really try to maintain more than 5-6, otherwise it gets too confusing. [ß]
The desktop application mostly Just Works[tm] with SSO. At least when M365 doesn't suffer from their 4-times-a-day auth outage.
ß: A lot of APIs and authentication systems were designed in the stone age. You either need a 1:1 permissioned access token that can do horrendous damage, or you deal with ultra-granular, confusing and ill-designed scoping jungle where nothing makes sense. Atlassian, I'm looking at you especially. At least an MCP server, provisioned with a reasonably done service account, doesn't have all of your powers to get things wrong with.