I’ve been using this in private Beta as a daily driver for about 6 months.
The team has been responsive, constantly improving, and bringing real innovation to the space.
Highly recommend!
Show HN: Warp, a Rust-based terminal
491–500 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#492Earlier quoted context omitted.
Agree, this is a pretty bad deal breaker for me. Big business people doing short-sighted big business things, salivating at cramming a product full of telemetry. All without transparency around it? In a terminal of all things?? Indescribably off-putting and catastrophically damages my trust in the product and the CEO. EDIT: To be fair there is some transparency in the original post. I was looking through the landing…
They have a complete telemetry section on their website where it also states that no input or output data is collected.
the problem with telemetry data is that sometimes you can accidentally collect sensitive data without realising it. i know one library on iOS was collecting the coordinates of all touch events. however, that meant it was collecting the coordinates of all touches on the keyboard which made it possible to reconstruct user input into password fields.
Re: Show HN: Warp, a Rust-based terminal
#493This is perhaps slightly orthogonal to the main discussion here on this thread, but I have a question for Zach (and the various engineers posting on this thread): Did you guys talk to real-world users while building this and before this launch? This whole blow-up re: your telemetry / open sourcey'ness seems like it could have been avoided. I'm curious if you actually floated these ideas with real world users and a) e…
There's an active Discord with 700+ Warp users. I reported issues on it and immediately got helpful replies. They're talking to lots of real-world users.
My take is that the hacker news crowd is not the target market for Warp. I think it does an amazing job of making the terminal easy and friendly to infrequent users. I'd recommend it to anyone who tells me they prefer a git GUI interface over the shell because of how confusing the shell is. (this is where Warp's completions really shine)
But if you're already very comfortable in the shell and have a customized setup there's some very rough parts of Warp. Lack of any compatibility with existing bash/zsh completions is the huge deal breaker for me.
Also you'd be surprised at the number of software engineers that really don't care how many sentry logging calls their apps make. I completely agree with the sentiment, and I personally just disable the Warp application's internet access to address this, but it's worth recognizing that we're in the minority of people that care.
Re: Show HN: Warp, a Rust-based terminal
#494Earlier quoted context omitted.
Agree, this is a pretty bad deal breaker for me. Big business people doing short-sighted big business things, salivating at cramming a product full of telemetry. All without transparency around it? In a terminal of all things?? Indescribably off-putting and catastrophically damages my trust in the product and the CEO. EDIT: To be fair there is some transparency in the original post. I was looking through the landing…
They have a complete telemetry section on their website where it also states that no input or output data is collected.
Which is worth nothing if it can't be examined and verified (not to mention it can change with any release).
Re: Show HN: Warp, a Rust-based terminal
#495So, I was excited by the idea of a terminal that added new functionality and wasn't electron based. So I downloaded Warp.
And, honestly, I can't use it. They interfere with the operation of the shell to such a degree that I had to disable almost my entire bash configuration.
Add to that, that I already have the following features native to bash shell (and I'm sure they're in zsh too):
- history of commands: easily searched by pressing ↑ or ⌃+r - completion: via the awesome bash-completion project - split panes: both terminal.app and screen do this for me - session sharing: screen + ssh does this for me - "workflow" sharing, I can and do write shell scripts that can be used by others
I've seen comments trying to defend this that REALLY make me doubt that the devs even understand how a terminal + shell work. A shell script will run in it's interpreter regardless of what shell you happen to use, shared commands will inherently be in the flavour of shell-script that the sharer is used to, and so i have to know how to use their shell as well as mine to translate between them, which again isn't a problem when running a script. They claim that people don't document their scripts, but the same people who won't document a script won't document stuff they share in warp. They claim there's no way to find documentation natively from the terminal or to search for scripts based on what they do, apparently they haven't heard of apropos and man pages?
Re: Show HN: Warp, a Rust-based terminal
#496Earlier quoted context omitted.
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.
> Absolutely nothing works better, it's the best by a ridiculously large margin. Then why is the telemetry-encrusted modern Windows a usability fail, even compared to past versions of Windows which relied on extensive in-house user testing?
Because power users turn off telemetry where they can which means they only see telemetry from "normal users".
That's my theory anyway.
Re: Show HN: Warp, a Rust-based terminal
#497Earlier quoted context omitted.
Wait, you _have_ to have a github account to even open this terminal? Yikes.
I remember an iOS email client many years ago that required a Dropbox login for some reason. It made no sense that an email client would require me to log in to a cloud file storage/syncing service - in my mind these two things are completely unrelated. That email client ended up disappearing. I expect that a terminal program which requires a login to a completely unrelated service will end up meeting the same fate a…
> an iOS email client many years ago that required a Dropbox login for some reason.
IIRC, that was Mailbox. Dropbox bought them a month after launch and then, sadly, killed it off two years later.[^1]
[1]: https://www.theverge.com/2015/12/8/9873268/why-dropbox-mailb...
Re: Show HN: Warp, a Rust-based terminal
#498Wanted 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 really wanted to like it, too. The screenshots look great
My thoughts exactly. I don't use potential keyloggers on my browser (think grammarly or similar), I'm not going to install a terminal making requests or getting my data as I use it.
Re: Show HN: Warp, a Rust-based terminal
#499this seems like brilliant tech that will unfortunately not succeed due to the business model. Cost/billing, forced outgoing requests, forced signup, and most of all, additional security risks. I'm not using a terminal with all my SSH keys if it is calling out to the internet.
Re: Show HN: Warp, a Rust-based terminal
#500If the business model for this was: 1) fully open source 2) ~$2.99 per user per month 3) more for team features 4) paid plugins and themes 5) opt-in and inspectable telemetry They’d probably get their million paying users in the first year. For this crucial part of this target market’s (engineers) toolkit, it HAS to A) be open source and B) have the option for zero telemetry. Inb4: “if it was open source why would pe…
Thanks for writing your thoughts! I can understand the skepticism and ultimately this is not far from the business we want to build.
The terminal is totally free for individuals and our business model is to make the terminal so useful for individuals that their companies will want to pay for the team features.
We are also definitely open-sourcing parts and potentially all of the code.
You can read more about how we see it here: https://github.com/warpdotdev/Warp/discussions/400.