zhengt

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.

Right now, login is required while we're in Open Beta.

When we GA, login will be opt-in (although you'd lose some of our cooler features).

Assuming you're on a shell that supports bracketed paste, it'll treat it as one block and execute all of the commands one after the other. The exit status will be that of the last command run.

Warp engineer here - thanks for writing about your experience!

As cieplik mentioned, it's true that telemetry has not been mentioned as frequently as it has been on HN.

> I think it does an amazing job of making the terminal easy and friendly to infrequent users.

As for our users, it's a combination of newer and more experienced terminal users. More than half of them are self-reported advanced or expert terminal users.

Thanks for your positive feedback, Divan!

cieplik did a great job implementing support for VoiceOver and having a few blind engineers beta test the app

This is for cloud-enabled features not presently in other terminals.

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.

Warp engineer here - Thanks for your response!

It's too early right now, but we are definitely going to open source parts and potentially all of the code.

Thanks for your response. Let us know how it goes with the app!

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 PARC & Apple Computer never happened.

The terminal is a surprisingly performance intensive application. When we built an initial prototype in electron, it was struggling to render full screens of text output on large screens. We want to support 144 fps on 4K monitors.

Additionally, Warp has GUI elements like blocks and context menus. We talk about performance because when we discuss our features, people automatically assume it's going to be sluggish.

Warp engineer here - Thanks for being an early user!

While folks have mentioned here that shells have powerful line editing capabilities, I've found that a lot of people miss this. We want to allow a broader set of people to be productive in the terminal. And FWIW, a lot of developers - with varying amounts of experience - have resonated with the text input.

Personally, I'm a heavy vim user and I've never gotten particularly comfortable using the shell's line editor.