Earlier 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…
This is why I deleted Fig ( https://fig.io/ ) right after installing it. It must've sent some uninstall information, too, because the creator/CEO emailed asking why I uninstalled it afterwards...
Show HN: Warp, a Rust-based terminal
341–350 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#342That's pretty cool. I'll be interested in trying it once all of the source is available. A proprietary terminal program that connects to googleapis.com, sentry.io, segment.io, etc. is a *total* non-starter for me.
Good luck with the beta! I'm really interested to see a release I'll be able to try.
(FWIW, I think the model, in macro, sounds like something I'm glad to support. It reminds me of Bitwarden, for which I happily pay every year.)
Re: Show HN: Warp, a Rust-based terminal
#343Wanted 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…
Re: Show HN: Warp, a Rust-based terminal
#344Wanted 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
#345Wanted 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…
Re: Show HN: Warp, a Rust-based terminal
#346I imagine if it was open source, didn't have a bunch of strange network calls built in, and most importantly a third party audited the source code to make sure you're not doing anything wrong, then I'd be open to trying it.
The issue here is you have a black box, which will have complete control over my system. I have no idea what happens the moment I give you my sudo password, do you install a bunch of weird stuff in the background? How do I know this isn't just a keylogger?
I can't imagine any company approving this for internal use.
Equally concerning, what's your business model. Are you selling my data ? Will you deliver ads straight to the terminal ?
At the same time, I would absolutely love to see you. Someone do this, but as a transparent open source project. I'm just not sure how you can create a business from that.
Re: Show HN: Warp, a Rust-based terminal
#347Earlier quoted context omitted.
I cant use it either (mostly because it's Mac only and also because of the sign-in requirement), but at least they are transparent about it : https://docs.warp.dev/getting-started/getting-started-with-w... https://docs.warp.dev/getting-started/privacy
That privacy policy is sketchy. It starts with this- > Our general philosophy is complete transparency and control of any data leaving your machine. This means that in general any data sharing is opt-in and under the control of the user, and you should be able to remove or export that data from our servers at any time. They then go on, further down the page, to say that this first paragraph is a complete lie- > Howev…
Re: Show HN: Warp, a Rust-based terminal
#348This is neat, but I'm not convinced it's going in the right direction. It's not open source, and "maybe it will eventually be" is unacceptable for such a core component of an engineer's workflow. Most of the features on the front page are "coming soon," not actually available. There's no timeline for support for non-Mac OS systems, and it's built using Metal rather than any cross-platform API, so it will be at least…
That's a huge overstatement. What's unacceptable about it (or any other software for that matter) closed-source?
Re: Show HN: Warp, a Rust-based terminal
#349Anyone 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
What do performance problems in a terminal even look like? I feel like a crazy person in this thread because I’ve literally never had the thought: “I could be so much more productive but this damn terminal is slowing me down”.
Most terminals don't even implement most well understood "hacks" to keep up with the apps they're running (e.g. "render" to a text buffer and render the text buffer to the screen separately and decoupled (multiplex or on separate threads)), because people rarely are affected enough to care.
Re: Show HN: Warp, a Rust-based terminal
#350Earlier quoted context omitted.
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.
Exactly, that's why people tend not to choose Windows for development unless they're forced to. edit: use -> choose
In my experience, most people who are developing software for Windows choose to use it to develop that software. There are a great many people who choose to develop software for Windows.