This is perhaps slightly orthogonal to the main discussion here on this thread, but I have a question for Zach (and the various engineers posting on this thread): Did you guys talk to real-world users while building this and before this launch? This whole blow-up re: your telemetry / open sourcey'ness seems like it could have been avoided. I'm curious if you actually floated these ideas with real world users and a) e…
Show HN: Warp, a Rust-based terminal
481–490 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#482Re: Show HN: Warp, a Rust-based terminal
#483Earlier quoted context omitted.
Why would it be easier to port Warp to a new system compared to Bash, Python, Perl, etc.? These tools are widely used to automate workflows and are already ported to any system you would probably care to develop on.
You aren't the one porting Warp, but you are the one porting the shell script.
Re: Show HN: Warp, a Rust-based terminal
#484Earlier quoted context omitted.
It's a good question, one that we are discussing a bunch. We are planning to first open-source our Rust UI framework, and then parts and potentially all of our client codebase. The server portion of Warp will remain closed-source for now. You can see how we’re thinking about open source here: https://github.com/warpdotdev/Warp/discussions/400 TLDR; As a side note, we are open sourcing our extension points as we go. T…
Why does it need a server? Is that normal for a terminal?
Right now, we have two relevant features: 1. The ability to share a "block" of input/output to a permalink that anyone can view. 2. A.I. command search.
Later on, for an individual, it may mean being able to sync settings across devices, fast setup of your terminal on new computers, and being able to access the command line on any device via the web.
For teams, it means we can build collaborative features. This does not mean just Google Docs-style real-time collaboration, but asynchronous collaboration through sharing commands, settings, and history. It means increased knowledge-sharing through wikis and READMEs that run directly in the terminal. It means making the terminal safer and more secure via integrated password-management and audit logging. It means making the terminal a more extensible and customizable platform, with a nice modern ecosystem.
The app works offline, just the two features I mentioned won't work.
Re: Show HN: Warp, a Rust-based terminal
#485Earlier quoted context omitted.
We are actively working on a11y! It's still a work-in-progress, but the goal is to a) make Warp the most accessible terminal there is and b) make a11y be an integrated part of the UI framework, so creating accessible apps in rust would be a no-brainer for future users of our framework. And yes - once we go cross-platform, we will work on the a11y support there too.
That's really lovely to hear, and to be honest, makes me more hopeful about the direction of the project in general.
Re: Show HN: Warp, a Rust-based terminal
#486Earlier quoted context omitted.
Vim supports multiline editing and I'd imagine emacs does as well. In bash/zsh, opens up $EDITOR so you can use whatever you're accustomed to anyhow. Most of these features are already available if one spends a bit of time configuring their terminal/shell.
While this can be done in zsh/bash, it takes investment to understand how to use multiline specifically. And then once you leave the terminal, the same keystroke does not do anything for you. One of Warp is that you don't have to think twice about it because it behaves similarly to text fields everywhere else on your computer. In the terminal, I often have the feeling that personal computing revolution from Xerox PAR…
Re: Show HN: Warp, a Rust-based terminal
#487Just tried it too.. Justified worries over closed-source & telemetry/github sign-in, but holy cow it's good. I especially like the just right minimal amount of settings – nothing extra, nothing missing – and fantastic minimalistic docs that gives understanding of all features and all hotkeys in like 10 mins. Impressive.
Re: Show HN: Warp, a Rust-based terminal
#488They’d probably get their million paying users in the first year.
For this crucial part of this target market’s (engineers) toolkit, it HAS to A) be open source and B) have the option for zero telemetry.
Inb4: “if it was open source why would people pay for it?!?” Because at the right price people are happy to pay and support something they love and get low-effort trustworthy updates built in.
Re: Show HN: Warp, a Rust-based terminal
#489Earlier quoted context omitted.
Usually the practice in these scenarios is to try out all possible ways to make out money and then go a little backwards once the public outcry is big enough. At some point you find the most profitable balance situation, before you have expelled all customers.
There is a plethora of free GPU-accelerated terminals. Alacritty, kitty, foot, wezterm, etc. None of these as far as I know send telemetry data. I see no reason to think that a new terminal is going to make money somehow by finding a balance.
I don't personally see any reason to swap terminal with telemetry. One of my worst fears that some day I am forced to.
Re: Show HN: Warp, a Rust-based terminal
#490This is perhaps slightly orthogonal to the main discussion here on this thread, but I have a question for Zach (and the various engineers posting on this thread): Did you guys talk to real-world users while building this and before this launch? This whole blow-up re: your telemetry / open sourcey'ness seems like it could have been avoided. I'm curious if you actually floated these ideas with real world users and a) e…
Is it possible that this is blowing up only on HN and the privacy thing is not regarded as so important in other communities?