Wanted 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…
Show HN: Warp, a Rust-based terminal
111–120 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#112Re: Show HN: Warp, a Rust-based terminal
#113> The terminal’s teletype-like interface has made it hard for the CLI to thrive
bullshit
> user accounts to just run a terminal?
bullshit
> collaboration
bullshit ...
Re: Show HN: Warp, a Rust-based terminal
#114Anyone know how this lines up to other terminals performance wise. I’ve been pretty happy with alacritty, but would be willing to try a terminal with more features. https://github.com/alacritty/alacritty
Kitty is awesome, but no windows if you're into that. Alacritty awesome as well, but minimalistic and rust which I have no idea why it matters in OPs post or in general.
Re: Show HN: Warp, a Rust-based terminal
#115Re: Show HN: Warp, a Rust-based terminal
#116> Telemetry > When Warp comes out of beta, telemetry will be opt-in and anonymous. > 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? ;-;
Warp engineer here. I understand your concern. We will remove telemetry when we enter general availability. It will be opt-in and anonymous. We really want to improve the product quickly during this beta phase. Collecting data 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:/…
Re: Show HN: Warp, a Rust-based terminal
#117They’ve raised $23m?!? Uhhh
I think you could build a really good terminal if you had $23M to piss away. I strongly doubt you can create a good terminal if it also needs a business model that can recoup $23M.
Re: Show HN: Warp, a Rust-based terminal
#118Wanted 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 feel bad for the engineers who worked on this, as this is really awesome but probably will not find market fit
Re: Show HN: Warp, a Rust-based terminal
#119Re: Show HN: Warp, a Rust-based terminal
#120> Telemetry > When Warp comes out of beta, telemetry will be opt-in and anonymous. > 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? ;-;
Warp engineer here. I understand your concern. We will remove telemetry when we enter general availability. It will be opt-in and anonymous. We really want to improve the product quickly during this beta phase. Collecting data 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:/…