Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

701–710 of 757 posts

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

#701

most devs just use the terminal in VSCode these days anyways. Are there _really_ enough terminal users and companies willing to shell out $$$ to make more than 1 million gross per year? This kind of reminds me of that prettification of the node repl fad a few years ago, but when they switched to pay only people were like "hard naw"

I did this for a while, but it's just more convenient to separate concerns and have long running sessions separate from IDE's restarts and crashes. As for the Warp's business plan - can't imagine there being many teams that would want this kind of complexity handled by terminal app and not CI pipeline.

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

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

> using up millions of VC-dollars building a new version of this fundamentally important core utility It's nice to think of this as 'taking advantage of' VC dollars, but VC dollars come with strings attached, namely the need for an 'exit'. The exit only happens if the company in question makes multiples of what it invested, meaning that VC-funded companies need significant revenue from their users. These days, the gr…

I'm already wary of creating accounts on VC funded apps. Surely there are others like this too. I'm just tired of being burned by the cycle you just described, eventually value must be extracted and usually that means a tradeoff of user values versus budget values and I'm not here for that anymore.

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

#703
post #298

Earlier quoted context omitted.

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…

There is a lot of constructive value in this comment, I hope it is internalized and thought about

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

#704

Earlier quoted context omitted.

They would not have used alacritty in that case.

Well, it doesn't look like they will be giving back. They will open source some things yes, but it doesn't look like it will go back into alacritty.

Which means it effectively makes no difference (for Alacritty) whether they use it or not.

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

#705

Earlier quoted context omitted.

I use Konsole. It's written in I-dont-know-and-dont-give-a-shit-why-is-that-even-relevant. It's free, does not spy on me, comes by default with Kubuntu and has great themes out of the box (including the Solarized themes).

> It's written in I-dont-know-and-dont-give-a-shit-why-is-that-even-relevant. Same. But boy to people really like tools "written in Rust".

If you knew you could double your upvotes and praise by including that phrase why wouldn't you? I mainly write Go these days but when I submit my next tool to HN I'm just going to name it YadaYada Pro Written In Rust and retire on all the resulting upvotes. Its a foolproof plan and don't you dare judge me for it.

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

#706

Earlier quoted context omitted.

Why even ask? Founders don't really have much control over what the tools they create wind up being used for. Assume that some people will use any tool you encounter for the worst thing it can possibly do. If the tool has significant potential to do things that bother you, don't use it.

Why do you say "wind up being used for" as if it is act of god rather than a business decision?

Because I'm talking about founders and how much control they have over the tools they bring into being.

Acts of God are a better model for that than business decisions.

Some users will abuse the snot out of it, and a small start up may not even realize that's happening for months.

The founder may not retain the authority to control decisions about what changes to make to the tools or how to monetize them.

Hackers may break into the servers and use the tool for their own ends.

And, yes, often enough the founder themselves will throw the users under the bus when push comes to shove.

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

#707

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.

But Windows Terminal is open-source and probably someday community will fork it to remove telemetry the way they did with VSCode.

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

#708
post #627

Earlier quoted context omitted.

> Incidentally, you might be interested to know that in the last 8 hours my comment has gotten 25 upvotes; that’s a lot of lost customers. No, that's a lot of people who upvoted your comment. I'd wager anyone who agrees with your perspective is unlikely to have been a Warp customer in the first place. (Speaking as one who tends towards your side of this discussion.)

I don’t mean that my comment cost them customers, only that the upvotes on my comment measures the customers they had already lost by using pervasive telemetry.

I doubt that even a plurality of the people who upvoted you would have installed Warp and wound up paying for it.

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

#709
post #162

If you want to use a terminal that is actually open source and doesn't have telemetry, much less only available via signing in with GitHub, use Alacritty, also written in Rust and cross platform. https://github.com/alacritty/alacritty

Or Kitty, which does more or less the same things but includes split and tabs and other convenience features.

Kitty is cool, I use it on debian, but it is not cross-platform. So I hesitate to compare it to alacritty.

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

#710
post #676
post #210

Earlier quoted context omitted.

This stuff has been in the major shells for years, through excellent editor integration. For emacs and vi it's pretty much free. If you want to integrate with a different editor, it's totally doable. Most of the stuff sibling comment is referring to center around the feature: 'edit-and-execute-command' in bash. There is a similar incantation for zsh. I summon it with, 'ESC v' in both.

Three words for 2 tests regarding these features: 1. discoverability 2. wide spread use. Bash and zsh fail both tests.

I love how my previous comment is downvoted with no answer by I assume bash and zsh fanboys when these kinds of features are barely used by users, because they can't be easily found.

Use something like fish to see what real feature discoverability for a shell looks like.

And I say this as a zsh user that has waded through the mountains of obscure documentation to set it up. Don't fall into Stockholm syndrome and think that if you went through hardship, others should, too.

99% of bash/zsh discussion threads are someone going: "here is awesome feature I found" (where frequently that feature is something that should have been painfully obvious to notice) and then 100 replies: "that's so cool and useful, I never knew about it and I've been using bash/zsh for N > 5 years".

Post reply on HN