Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

361–370 of 757 posts

Re: Show HN: Warp, a Rust-based terminal

#361
post #20

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…

Just curious, what tools do you prefer to use to identify network requests from recently installed applications such as this?

On the mac there's Little Snitch.

Re: Show HN: Warp, a Rust-based terminal

#362
> I’m Zach, founder and CEO of Warp

You started a company to write a terminal app? I'd say that's either misguided, or you have something underhanded planned.

> any Mac user can download it.

Any _Mac_ user? Sounds fishy.

> The terminal’s teletype-like interface has made it hard for the CLI to thrive.

Isn't that an anti-tautology? Hmm.

> An input area that works just like a code editor

Why wouldn't I just use a code editor? We are talking about an app for graphical desktop environments, right?

> ... with GPU-accelerated graphics

That you wrote especially for this app? I don't know...

> We are planning to first open-source our Rust UI framework, and then parts and potentially all of our client.

A _closed-source_ terminal app? Nuh-uh. You're up to no good.

----

And after noticing those red flags, I read @orastor's post about the app connecting to all sorts of servers.

Re: Show HN: Warp, a Rust-based terminal

#363
post #99
post #20

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…

Also: security? I expect my terminal to be a much more secure environment than my web browser. When an application starts communicating with the internet, I have no choice but to treat it with the same level of scrutiny as my browser. Even making telemetry opt-in means that it has the capability to send information to the internet that I don’t know about, which means that I have to treat it like an application that c…

This was my first concern as well. I don't want my terminal to be a startup.

Re: Show HN: Warp, a Rust-based terminal

#364
post #44

Earlier quoted context omitted.

I'm not sure I'm ready to have SaaS models replace core utilities and tools locally. > Announcing Warp’s Series A: $17M to build a better terminal And just thinking about this... it's not clear to me what their moat will be as I suspect if there's a really compelling feature it will be available in OSS terminals quite quickly. Perhaps it's the product polish? But I'm not sure polish is what I want from a terminal, at…

I doubt their compelling features will be in OSS terminals any time soon. I’ve wanted a terminal that has a decent multi line editor for years , and there’s nothing out there.

I use pretty out of the box zsh with vi-mode and it... just works for multiline editing? I can simply move down and up with j/k...

Re: Show HN: Warp, a Rust-based terminal

#365
post #109

Earlier quoted context omitted.

From their link, it seems they don’t. Agree that positive confirmation would be good, for beta. > We do not store any data from the command input or output itself as part of our telemetry.

This is correct. We do not send or store any terminal contents (input or outputs) to our server. The only case in which that is not true is if a user elects to use Warp to share the output of a command using our Block Sharing feature.

With the rest of your responses I'm left looking for weasel words in here.

Re: Show HN: Warp, a Rust-based terminal

#366

Earlier quoted context omitted.

or they actually listen to our feedback, remove forced telemetry, remove sign-in in the next release, then i'd be more happy to give their product another chance although no guarantee they'll not turn evil at some point in the future...

If they start out evil, then don't expect them to change.

Wanting to collect usage information and errors isn't evil-by-default. It's incomparably useful for troubleshooting and improving. Absolutely nothing works better, it's the best by a ridiculously large margin.

But yeah, terminals are very sensitive environments, opt-in should be a default even at launch.

Re: Show HN: Warp, a Rust-based terminal

#367
post #44
post #20

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'm not sure I'm ready to have SaaS models replace core utilities and tools locally. > Announcing Warp’s Series A: $17M to build a better terminal And just thinking about this... it's not clear to me what their moat will be as I suspect if there's a really compelling feature it will be available in OSS terminals quite quickly. Perhaps it's the product polish? But I'm not sure polish is what I want from a terminal, at…

I wondered the same. Then I realized it sends out requests to googleapis, segment, and sentry. Imagine having data on every dev's terminal workflow? Ca$h.

Re: Show HN: Warp, a Rust-based terminal

#368
post #20

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…

At least for EU users, you cannot collect information like this without the explicit consent of those users.

It's 2022 FFS, and still companies are over-stepping the mark - companies behaving like yours are exactly the reason GDPR and ePrivacy etc exist in the first place :/

Re: Show HN: Warp, a Rust-based terminal

#369

It looks nice but I'd never use a shell that phone's home. Period. I mean the CLI has been one of the last parts of my system that I really still trust is working on my behalf only. This product made me rethink that assumption. As for capturing the output from a command line on the mac (and also on linux IIRC) just use pbcopy/pbpaste. My opinion: It's not worth giving your privacy away for features like this.

Do you use Windows? Have you ever opened its terminal? Congrats, you're using a terminal that you agreed can phone home with telemtry. See https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk... and the link to the privacy policy for windows terminal http://go.microsoft.com/fwlink/?LinkID=521839 I suspect OSX is no different and has similar telemetry and privacy policy for its terminal.

> Do you use Windows?

Whenever I do that, I can never decide whether it's me who's using Windows or Windows that's using me :-(

Re: Show HN: Warp, a Rust-based terminal

#370
This is really interesting. I have been annoyed for a long time on how ssh, the terminal emulator, tmux, and the shell don't know anything about each other. I also started writing a native terminal emulator (no electron, of course) to fix these problems. I kind of thought I'd do the slow burn over 4 or 5 years of using it myself (being a shell sadly means writing a programming language, and you don't make a good one over the weekend), then maybe stick it on Github and get a Patreon going if other people want to use it and could be convinced for something they can get for free.

Warp has taken a dramatically different approach; they got millions in funding and just made it a company. I am shocked because I never considered there was a market for these things. Developers hate having their tools taken away when their credit card expires, and it's kind of hard to compete with free, which clearly works well enough to have created all software and systems currently in existence. But I guess there was a time when you only got a UNIX shell with a commercial UNIX license, and people did somehow get access to those, and they did become very popular.

Anyway, seeing this really made me rethink the world and I'm still reeling a little bit. (I think my thing will be better though ;)

Post reply on HN