[zachlloyd]

Our plan is to open source the Rust client code once it's more mature.

We are particularly excited about sharing our Rust UI framework since there aren't a lot of great options for building native UIs in Rust right now. We want to make it cross-platform first though.

[raphlinus]

There are a lot of promising options for native UI, but none finished and mature. As of today, that number sounds like it is one more.

Druid as it exists today is not a great fit for what you're trying to do, as drawing on mac is all based on Core Graphics and Core Text. GPU-based drawing is the future, and we're working on that (piet-gpu), but it's not yet in a really usable state.

In any case, hope this goes well. It's clear to me that Rust-based UI is the most viable path to an Electron alternative in the future, and the more evidence we have for that, the better.

[alokedesai]

Thank you, Raph! We've been following your work on Druid quite closely for a while, it's very impressive.

You'd exactly right that's why we didn't pick Druid--we needed something that rendered on the GPU. We actually talk more about this decision in our "How Warp Works" blog post here: https://blog.warp.dev/how-warp-works/

[kaetemi]

Why not just develop out in the open from the start, instead of dangling an open source carrot? You might even get community contributions.

[zachlloyd]

It's a fair point, but we don't feel ready to accept community contributions yet.

[cweagans]

You really don't have to accept contributions if the repo is open. You could simply disable issues and close all PRs with a comment explaining that you're not ready for contributions yet. You could even automate that with a Github Action or similar.

Developing in the open would make it easier to trust that you're not doing something nefarious. When I think about the kind of data that goes through my terminal on a day-to-day basis, I have to _know_ for sure that my terminal can be trusted. That makes Warp a non-starter for me until it's open source, which is really a shame because it looks fantastic.

[lyxell]

What about the UI framework druid? It has 3.9k stars on Github and is under active development.

https://github.com/linebender/druid

[alokedesai]

It's definitely something we actively considered! You can find some more details about why we chose to implement our own UI framework here: https://blog.warp.dev/how-warp-works/. The tldr; for Druid is they don't support any GPU backend at all right now.

[nicoburns]

Super excited about both of these things. Will your text editing widget be part of that? Because I'd absolutely love it if a widget with capabilities similar to that of full on text editor (sublime/vs code, etc) became the standard "textarea widget".

[techrat]

> Our plan is to open source the Rust client code once it's more mature.

Your plan should have been to wait until something was downloadable before you announced it.

[myWindoonn]

https://xkcd.com/463/ Strictly speaking, your plan is better than the alternative of keeping it closed-source, yet someone is clearly doing their job horribly wrong.

Anything useful you produce will be community-maintained eventually, and your cloud product will vanish once you complete your amazing journey; anything in-between seems like rent-seeking. Meanwhile, your competitors are Free Software and can out-develop you.