To add more color to some of your points in the post above:

* We give users the option to disable telemetry before sending any back to our servers.

* We use Sentry for crash reporting, this can be disabled.

* Yes, we record telemetry with the option to disable. The events are in our source code (as you point out) and also on our website.

* We have a network log in app that you can open and view _any_ request we make, including requests to send telemetry.

* If you compile the OSS build it has no telemetry or crash reporting.

Our motivation with open sourcing is to build more trust with our community, not less. Happy to discuss more and, of course, the codebase is available to audit.

no requirement to use it--and you can turn off all of the AI features if you don't want to use them at all

We've actually added a ton of controls recently to let users configure how much (or little) UI they want. If that's not enough, would love if you opened an issue on the Warp repo and we can discuss more what needs to change in the product to meet your needs!

Comments URL: https://news.ycombinator.com/item?id=42390896

Points: 2

# Comments: 0

No ETA for this yet, but this is very much on our radar to fix asap.

Comments URL: https://news.ycombinator.com/item?id=41983544

Points: 5

# Comments: 1

I’m really excited to share that Warp is now available on Linux! If you’re interested in trying it out, you can download Warp at https://www.warp.dev/.

We've gotten 2-3 reports of authentication issues like the one the author mentions. We are actively looking into it; we believe its an issue with a library we depend on to open URLs. If anyone is experiencing these issues, please contact us at support@warp.dev so we can better understand the issue and further debug!

Building Warp on Linux was quite an undertaking. Warp uses a custom Rust-based UI framework that we built in house and renders natively on the GPU. To get Warp running on Linux, we built a version of our UI framework that supports winit [1] as a windowing backend. We also built a version of our renderer that uses wgpu [2]. Reducing complexity by using these well-supported, cross platform, frameworks let us bootstrap a version of Linux quicker than expected and should make it easier to build Warp for other platforms (like Windows).

Please let me know what you think! Happy to answer any questions, either about the product or about technical challenges.

[1] https://github.com/rust-windowing/winit [2] https://github.com/gfx-rs/wgpu

I’m really excited to share that Warp is now available on Linux! If you’re interested in trying it out, you can download Warp: https://warp.dev/

Building Warp on Linux was quite an undertaking. Warp uses a custom Rust-based UI framework that we built in house and renders natively on the GPU. To get Warp running on Linux, we built a version of our UI framework that supports winit [1] as a windowing backend. We also built a version of our renderer that uses wgpu [2]. Reducing complexity by using these well-supported, cross platform, frameworks let us bootstrap a version of Linux quicker than expected and should make it easier to build Warp for other platforms (like Windows).

Please let me know what you think! Happy to answer any questions, either about the product or about technical challenges.

[1] https://github.com/rust-windowing/winit [2] https://github.com/gfx-rs/wgpu

I'd love to hear more about the rendering issues you've faced when using Warp so we can fix them!

Warp requires a login to support its collaboration features (for example sharing commands with a team). Login makes it possible for developers to collaborate securely.

[1] https://docs.warp.dev/features/network-log [2] https://docs.warp.dev/getting-started/privacy#exhaustive-tel...

If you are interested in trying Warp (including our new collaboration features), you can download Warp here: https://www.warp.dev

The best part is chiseling ice cubes from a large clear block of ice: use a serrated knife and a hammer and you will end up with perfectly square blocks of ice.

Comments URL: https://news.ycombinator.com/item?id=35727527

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=35262652

Points: 1

# Comments: 0

This is a great article! Writing a custom UI framework to render on the GPU is a big cost--but it has been worth it for us. It has let us build a UI-heavy terminal while continuing to match the performance of some of the fastest terminals on the market (such as Alacritty). There is certainly an initial velocity hit for new engineers as they have to learn the semantics of our framework, but overall I wouldn't say it has a big detriment on our velocity as a consumer of the framework.

The callout to a11y is a good one--we have basic a11y support but it is by no means robust. There are additional downsides to building your own GPU-rendered UI framework other than a11y that I want to call out: you have to build most of the interactions with the platform yourself instead of getting it for free when rendering using system APIs.

One example of this is properly supporting i18n. A robust framework should support RTL text, positioning IME / the emoji picker, so forth. While implementing these yourself is doable (we have decent support for IME at Warp, for example) it requires an engineer or two to spend a few weeks to implement.

Text rendering is also a beast, see https://www.warp.dev/blog/adventures-text-rendering-kerning-....

For Warp, this has definitely been worth it, but it hints that the community needs better cross-platform GPU-rendered UI frameworks so people don't need to consistently build them themselves.

Comments URL: https://news.ycombinator.com/item?id=34342438

Points: 156

# Comments: 54