Show HN: Warp, a Rust-based terminal
31–40 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#32This is neat, but I'm not convinced it's going in the right direction. It's not open source, and "maybe it will eventually be" is unacceptable for such a core component of an engineer's workflow. Most of the features on the front page are "coming soon," not actually available. There's no timeline for support for non-Mac OS systems, and it's built using Metal rather than any cross-platform API, so it will be at least…
Re: Show HN: Warp, a Rust-based terminal
#33Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
Re: Show HN: Warp, a Rust-based terminal
#34Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
I definitely understand the concerns. For our public beta, we do send telemetry and associate it with the logged in user because it makes it much easier to reach out and get feedback when something goes wrong. But we only track metadata, never console output. For an exhaustive list of events that we track, see here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... . Once we hit general availability, ou…
Honestly opting in by default is, at least in my opinion, not acceptable.
People who would say no to that popup would not appreciate you randomly reaching out to them anyway.
Re: Show HN: Warp, a Rust-based terminal
#35> But for our beta phase, we do send telemetry by default and we do associate it with the logged in user because it makes it much easier to reach out and get feedback when something goes wrong.
This is a hard pass for me, it looks really amazing though. I'm so tired of telemetry, how do we quit our day jobs to focus on open source? ;-;
Re: Show HN: Warp, a Rust-based terminal
#36Re: Show HN: Warp, a Rust-based terminal
#37Re: Show HN: Warp, a Rust-based terminal
#38When someone uses "re-imagined from the ground up" I expect that this terminal will not function like any other terminal I've seen before. Yet it looks exactly the same.
Re: Show HN: Warp, a Rust-based terminal
#39Is your plan to open-source this or open-source its core in the future?
It's a good question, one that we are discussing a bunch. We are planning to first open-source our Rust UI framework, and then parts and potentially all of our client codebase. The server portion of Warp will remain closed-source for now. You can see how we’re thinking about open source here: https://github.com/warpdotdev/Warp/discussions/400 TLDR; As a side note, we are open sourcing our extension points as we go. T…
Re: Show HN: Warp, a Rust-based terminal
#40I've been loving Warp since discovering it on HN a few months back. I was originally drawn in by how it treats text input like a regular text input field out of the box, so I don't have to configure anything and my normal text editing shortcuts just work. But the other features of it have been really great too. I like the terminal splitting, the history searching, the command palette, and no performance issues I've n…