Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

321–330 of 757 posts

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

#321

Earlier quoted context omitted.

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…

That's a ton of data being collected. I would rather much have this submitted during a crash, rather than opt-in/opt-out. I'd not want to use a terminal that has data collection that crosses the internet every time I use it.

Totally understand if you don't feel comfortable using it!

The reason we don't submit this only during a crash, is because there are a lot of other things we want to know about users like: Which features are they using? Are they sticking to warp as their daily driver? How much time do they spend in the app?

We do want to make the telemetry opt-in after Warp is out of beta.

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

#322
Not much new to say, just my $0.02.

- Love the idea overall of a fresh, new shell. I love novelty, features, ergonomics, and this pushes all the right buttons

- Looks gorgeous

- The mandatory Github login is...weird. I don't mind logging in, but it seemed unskippable, and conceptually that leaves a bad taste.

- Mandatory telemetry...ehhh. Like I get it, I use Sentry and OTEL, I love the visibility, and I get exactly why you want it in the beta, but ehhhh, really bad look. Especially in this community. Also the privacy policy doesn't seem to be linked from the app. I can get to it, but would be nice to just go there right from the about page. On the whole...I find it tolerable, but I don't work in a highly sensitive field at the moment. At $LASTCO, that would be a complete nonstarter. Between the squick factor and compliance, it would be good to at least allow some amount of opt-out on the phone home.

- I would easily pay $20-50 for a souped-up terminal (I spend all day in it), even a closed-source one, but the "we raised tons of money to build a free terminal and haven't figured out how to monetize it yet", again, understandable, but not the best look, given the mandatory data collection. Hey, dev's gotta eat, but I'd rather pay for OSS and transparency, rather than free-but-you-are-the-product, and I hope they go for the former route.

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

#324
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…

Yeah. From a developer standpoint my terminal is the one sacred thing i have still. Im unfortunately not using something that is going to randomly break or make external calls every time I open it.

Looks cool but I will never even give this a try.

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

#325

It looks great. If I can live with sublimetext being closed source I’m sure I can live with my terminal also being closed source. Heck the windows terminal and macOS terminal are closed source and I use them everyday.

Microsoft open sourced their terminal components a little while ago https://github.com/microsoft/terminal The team at Microsoft managing this are super responsive on Twitter https://twitter.com/DHowett https://twitter.com/cinnamon_msft

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

#327
Excitedly downloaded this, launched it, and then was met with a login screen. wop wop. I closed it and deleted it.

I don't understand. Why is login a requirement to even use it?

Why not have an excellent free terminal as a way to get people using your tools, and then add the collaborative/audit features as paid features? That way many devs would not only start using this, but can make it a part of their daily workflows.

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

#328

Earlier quoted context omitted.

It's just.. an incredibly bad look to have this be the top comment on a post about this while the website claims that "cloud stuff" is opt-in. It's more essential to be honest about this during the beta period than after, so "oh it will be opt in" is a cold comfort, alongside the approximately never-true "we'll open source it some day." Not touching this with a ten foot pole. Not for something as essential to my day…

We tried to be really upfront in the privacy policy: https://www.warp.dev/privacy Opt-in refers to anything that sends any contents of a terminal session to our servers (as opposed to telemetry which is metadata and never contains any terminal input or output). But we hear the feedback and appreciate it.

That doesn't fit people's normal expectations. You're being intentionally deceptive.

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

#329

Earlier quoted context omitted.

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.

I appreciate memory safety in applications that handle and interpret data controlled by third-parties. Kitty and Alacritty stand apart as written in memory safe languages, unlike the vast majority of terminal emulators which are written in C/C++. Doesn't mean their bug-free, but they're less likely to have trivial RCE vulnerabilities.

Kitty is written in C, afaik.

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

#330

Why do I get the sinking feeling that the comments here are going to turn out to be like "No wireless. Less space than a Nomad. Lame."; and despite looking like the Juicero of terminal emulators now, Warp will be table stakes for any upcoming developer 10 years from now, who will be unable to fathom using a bare shell in xterm or even something like Kitty?

What makes you think that other terminals like https://github.com/alacritty/alacritty or https://github.com/kovidgoyal/kitty can't catch-up in features?

For one, closed-source is a non starter to many and I only see this trend going up.

No, this is not a dropbox-like launch. And criticism seems pretty fair so far.

Post reply on HN