Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

261–270 of 757 posts

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

#261

It looks nice but I'd never use a shell that phone's home. Period. I mean the CLI has been one of the last parts of my system that I really still trust is working on my behalf only. This product made me rethink that assumption. As for capturing the output from a command line on the mac (and also on linux IIRC) just use pbcopy/pbpaste. My opinion: It's not worth giving your privacy away for features like this.

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.

Would you expect anything less than a product from the first company to lie down for the NSA?

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

#262

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…

> 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!

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

#264

"[we want a restrictive license that] prevents another company from starting a commercial enterprise off of it" versus "our terminal model code is based on Alacritty’s model code." Well done. Sorry guys, that's where you lost me.

I understand where you're coming from.

My take is that there are plenty of commercial projects that have open source dependencies so it's not quite so black and white. That said we are still figuring out the best way to proceed on open sourcing the warp client code.

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

#265

It looks nice but I'd never use a shell that phone's home. Period. I mean the CLI has been one of the last parts of my system that I really still trust is working on my behalf only. This product made me rethink that assumption. As for capturing the output from a command line on the mac (and also on linux IIRC) just use pbcopy/pbpaste. My opinion: It's not worth giving your privacy away for features like this.

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.

> forgets linux exists

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

#266
post #194

This 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 ...

Actually I would say collaboration is a huge win. Right now we do shared screens when we have to do some CLI operation. I know and have worked at companies with very complicated setups for CLI-based workflows where you need 2 people to agree for each command. This could potentially solve all of that. That being said, with the move to containers there's a lot less CLI surgery to do.

But hasn't collaboration and stuff been a thing for as long as time-sharing machines have? Besides, Service as a Software Substitute is NEVER a good idea, I don't want to go to someone else's server to do something I could on my own, especially when I have to pay taxes for it... By the way, can you define "CLI surgery" for me? I used Unix for a while but haven't played with containers beside chroot jails, and I suspect all that is just your company overcomplicating simple things.

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

#267
post #173

Earlier quoted context omitted.

Yeah, this is a known issue, unfortunately--but it's definitely something we want to fix as we improve Warp. See more information here where we chat with Casey about it: https://twitter.com/zachlloydtweets/status/14175482714432348...

> we should generally be at, or near, the performance of Alacritty > evidence that it’s not > Yeah, this is a known issue I don’t want to be critical, but which is it? If you know you are not anywhere near the performance, why say you are?

> If you know you are not anywhere near the performance, why say you are?

(in a voice like Jon Lovitz as Master Thespian) Marketing!

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

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

well, they gotta pay back those $17M to investors !

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

#270

"[we want a restrictive license that] prevents another company from starting a commercial enterprise off of it" versus "our terminal model code is based on Alacritty’s model code." Well done. Sorry guys, that's where you lost me.

I understand where you're coming from. My take is that there are plenty of commercial projects that have open source dependencies so it's not quite so black and white. That said we are still figuring out the best way to proceed on open sourcing the warp client code.

Yes there are plenty of those. And if they then blatantly state that they are not open source because they don't want somebody to build a business on their product while that's exactly what they are doing, then they lost me as well.

I really like what you guys are working on, and I'd absolutely give it a try. But this is really a deal breaker here. Make the team-oriented features proprietary that need server space and accounts and all that, open-source the rest and enable it to run offline. Maybe not tomorrow, I get that. But the moment you do this will open the dams. Until then, you'll stay in a niche.

Post reply on HN