The Conductor Rewrite: What They Changed to Make It Fast

(performance.dev)

11 points | by Charlieholtz 2 days ago ago

5 comments

  • tymonPartyLate 16 hours ago ago

    This post is clearly an ad disguised as a technical article, but Conductor is a fantastic tool, so I'd like to post some questions regardless. How can they have product-market fit if this is a free product? How can they know the customers' willingness to pay for it there are no payments? Or has it been tested? How can this be worth a $ 22M series A if its a UX layer on top of Claude that can be easily copied by Anthropic?

    • rbinv 16 hours ago ago

      People will pay for a good workflow/orchestration layer around coding models, see Cursor. I agree about the moat though, seems fragile.

  • videlov 16 hours ago ago

    Surprised to see they kept Tauri. In our experience of using Tauri, it has been a significant source of compatibility and performance issues related to it's use of WebKit and WebKitGTK. So much so that we have started an effort of migrating away from it for our app, in favor of Electron (https://github.com/gitbutlerapp/gitbutler/tree/master/apps/l...) The choice was made specifically for the benefit of our users, but we were also pleasantly surprised by how much better the development experience is with it.

  • rbinv 16 hours ago ago

    I find it refreshing to see dev tools competing on latency again. Has anyone tried both Conductor and Zed for agentic coding on a real project? How do they compare?

  • albertgoeswoof 16 hours ago ago

    [dead]