Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

291–300 of 757 posts

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

#291
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’ve wanted a terminal that has a decent multi line editor for years, and there’s nothing out there.

You can go the other direction.

Install neovim. Run `:terminal`. optionally run `:help Terminal-mode` first so you can figure out how to get out.

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

#292

Earlier quoted context omitted.

Warp engineer here. Really appreciate your ideas here! > Warp's more visual completion is super welcome. Does it work with the shell's standard completion scripts? It does not. But we have completions out of the box for 200 commands. Warp's input is a text editor instead of the shell input. This means we ended up building completions by hand and soon, via the community. We think this is a better experience because we…

> This means we ended up building completions by hand and soon, via the community. You like people to contribute for free ("build a community") but refuse to give them an actual FOSS client. This is bound to fail. There are ways to make this go both ways though, and I hope you'll make them work once you are a bit further along in your journey. Exciting project!

> You like people to contribute for free ("build a community") but refuse to give them an actual FOSS client. This is bound to fail.

Sublime text has a pretty active community that builds and shares extensions.

Why not warp?

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

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

Wow, this is just unbelievable. You don't say anywhere on your privacy page that you are associating this data with specific users.

Everything your company says regarding privacy seems to be a complete lie. You contradict yourselves everywhere. As a security officer I would never allow any company whose security I run to use your product- even if you fix this issues now who knows if you're going to lie again in the future.

Trust is hard to regain once lost, and your company definitely blew it here.

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

#294

Like others here, I'm leery of replacing my terminal with a VC-backed, maybe open-sourced eventually product, and a bit annoyed it claimed a name already in use in the Rust world. But...it is exciting to see someone reimagining the terminal a bit. People frequently talk about wanting a better GUI interaction model for everyone, but the actual ideas to improve it seem to be missing, I think because the desktop status…

Warp engineer here. Really appreciate your ideas here! > Warp's more visual completion is super welcome. Does it work with the shell's standard completion scripts? It does not. But we have completions out of the box for 200 commands. Warp's input is a text editor instead of the shell input. This means we ended up building completions by hand and soon, via the community. We think this is a better experience because we…

How about we don’t downvote the developers when they take time to answer questions?

I don’t care if it wasn’t the answer you were hoping for -this should be upvoted as it is very relevant for the conversation in this thread.

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

#295

Earlier quoted context omitted.

Yes, that is true, but it does seem like that's what their strategy is. If you're using these collaboration tools at your job, you'd have to be using the product already. So that's less of a problem than it would be for say, scripts included with some sort of open source project. My point is mostly that shell isn't cross-platform, and this is one way you could address that. But it's not a generalized solution, absolu…

>shell isn't cross-platform basically every operating system has a posix shell by default except windows, but it has been ported there multiple times, samba existed for decades and WSL is on the rise. It may sound a little more irritating but they deserve it for still running windows :p /hj (besides you can just host an ssh server)

I mean, I could also tell you "Just download and run PowerShell, it's ported to Linux", but you also know that would make you feel like a second-class citizen, because you know it's not something as good as something that actually works on your platform in a real sense.

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

#296

I assume Warp is fundamentally incompatible with GNU screen or tmux. That's a shame because terminal multiplexers like GNU screen and tmux such a core part of my terminal usage that I'm hesitant to discard them, even for something that looks really useful like Warp. I'm not sure how many people actively use terminal multiplexers like GNU screen and tmux, so maybe I represent only a tiny minority of users.

On the beta sign up survey they mention tmux as a feature request.

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

#297

Earlier quoted context omitted.

We potentially could remove the telemetry sooner, before the general availability. There is no set timeline yet, but we will announce it when we do!

you need to realise is that if you don't do this "by tomorrow", the momentum will be lost and no HN'er will ever use your product, because they will forever associate it with tracking

This is already being brought up in multiple slack networks I'm on, with the general consensus being that these decisions make the company impossible to trust.

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

#298
post #132

There are some legitimate concerns about Warp throughout these comments (telemetry, business model, etc.). But the one thing that really excites me is to have a full team working full-time on building the terminal that developers want to use. They're doing real user research, talking to developers, and taking feedback in forums like HN seriously - and using up millions of VC-dollars building a new version of this fun…

Thanks kyeb. I agree with both points here - we need to be very careful and sensitive in terms of how we build this product from a privacy and security perspective, but we see the opportunity mostly the same way you do. There are some great open source terminals out there, but having the opportunity to rethink it with a team of dedicated full-time engineers I think gives us an opportunity to build something really po…

Not to mince words, but so far you've made a very basic series of unforced errors on both privacy and security. This is perhaps to be expected, as glancing at your About page, you don't seem to have any security or privacy specialists on staff. I don't even see a security page or contact info.

Warp is starting to read like a Product-driven startup. The kind where people figure security and privacy are little features you can just throw in at the end of the dev cycle and advertise until then. It's not like anybody is going to actually check or care, right?

It's an understandable error in a visionary. Yet it's not the kind of mindset that produces trustworthy, secure, privacy-respecting enterprise products that companies happily pay lots for.

You're absolutely right. Warp needs to be very careful and sensitive about privacy and security. It may be worth reflecting on why you haven't been so far.

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

#299
Well I think this looks really cool! I’d be interested if it just had Blocks and nothing more, but the other headline features for individuals sound great too. I’m not sure how much value I’d get out of the team features, but I’m certainly open to being pleasantly surprised.

And I don’t mind using my GitHub account or contributing to telemetry during a private beta. I understand why others here find that problematic, but I’ll probably just use another terminal if I need to use/access sensitive data during that period.

Looking forward to trying this out! Thank you for sharing.

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

#300
post #59
post #35

> Telemetry > When Warp comes out of beta, telemetry will be opt-in and anonymous. > But for our beta phase, we do send telemetry by default and we do associate it with the logged in user because it makes it much easier to reach out and get feedback when something goes wrong. This is a hard pass for me, it looks really amazing though. I'm so tired of telemetry, how do we quit our day jobs to focus on open source? ;-;

Warp engineer here. I understand your concern. We will remove telemetry when we enter general availability. It will be opt-in and anonymous. We really want to improve the product quickly during this beta phase. Collecting data 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:/…

> never console output.

Hopefully also not input ;)

Post reply on HN