A terminal that makes you sign in? I think I'll stay away from this one.
Show HN: Warp, a Rust-based terminal
531–540 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#532Earlier quoted context omitted.
You aren't the one porting Warp, but you are the one porting the shell script.
So programs/workflows written in Warp will be portable without much effort, in some way that an equivalent shell or python script isn't? Why do you think that?
Thats a good question. In the end Warp programs/scripts will be written in just yet another interpreted language.
Re: Show HN: Warp, a Rust-based terminal
#533This 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 ho…
> 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.
I'm in this boat. I never understood why I should care if some website interacts with google apis or logs everything I do and sells it to marketers so they can sell me ads. I'll block them anyway so it'll never make a difference to me one way or the other.
Re: Show HN: Warp, a Rust-based terminal
#534This is bullshit. > 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 ...
Please contribute more elaborative criticism than simply the word "bullshit"
Re: Show HN: Warp, a Rust-based terminal
#535Earlier 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.
Zach, this telemetry approach is fine for Google Docs retail users but Warp's target customers are some of the tech savviest people on the planet. They are going to hold Warp to much higher standards of security and privacy.
Second, your user onboarding has too much friction with mandatory Github logins. You need an advisor / product manager who can guide you better when making these "human" decisions.
Re: Show HN: Warp, a Rust-based terminal
#536Earlier 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…
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...
Profit motive means that even if they do that now, they're incentivized to collect data in the future. From the standpoint of investors, leaving that revenue stream on the table would be dumb, considering every other company in tech spaces draws revenue from collecting their customers' data.
If a company is committed to never spying, then they'd have no problem making such terms contractually binding on their end. Companies that say they're against spying, but leave the option to collect their users' data open for the future, aren't really committed to not spying.
Re: Show HN: Warp, a Rust-based terminal
#537Earlier quoted context omitted.
“Command not found: git. Did you mean github(tm)?”
You've reached your daily execution limit of `git`, please buy Warp tokens through the Warp Store (F4) to continue using `git`.
I think you mean “please buy warp keys to unlock git boxes. 1 in 10 give you a rebase token! Each git box has at least one commit token. Follow us on twitter so you can be the first in line when our ascii art NFTs go live!”
Re: Show HN: Warp, a Rust-based terminal
#538Are you using an IMGUI library or some Electron-like solution for the GUI?
Re: Show HN: Warp, a Rust-based terminal
#539Negatory. Go fsck yourself.
Re: Show HN: Warp, a Rust-based terminal
#540Earlier quoted context omitted.
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.
Telemetry is just the cheapest and most convenient option for business owners, and not necessarily the best option when it comes to improving customer value and experiences.
Case studies, focus groups, surveys and interviews are great ways to determine usage patterns and problems with products and services. Of course, you'd need to pay users to participate in them, and then you need to pay expensive employees to conduct, collect and analyze the results. Spying is cheaper than doing any of that.