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

511–520 of 757 posts

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

#511

Post by zhengt »

CamJN wrote: post #495

So, I was excited by the idea of a terminal that added new functionality and wasn't electron based. So I downloaded Warp. And, honestly, I can't use it. They interfere with the operation of the shell to such a degree that I had to disable almost my entire bash configuration. Add to that, that I already have the following features native to bash shell (and I'm sure they're in zsh too): - history of commands: easily se…

Warp engineer here! The shell has arbitrary access to the environment, and there's a long tail of shell config to play nice with. For example, here's a fun technical read about how we supported PS1 and how the 9c byte caused some issues (https://www.warp.dev/blog/whats-so-special-about-ps1). We've prioritized issues based on the impact for the product. If you're up for it, I'd love if you could file some issues about the problems you're experiencing.

There are a lot of great shell configs. One advantage of Warp is that the terminal & shell have these features out-of-the-box.

> A shell script will run in it's interpreter regardless of what shell you happen to use, shared commands will inherently be in the flavour of shell-script that the sharer is used to, and so i have to know how to use their shell as well as mine to translate between them, which again isn't a problem when running a script.

Workflows in Warp specify the shell in the metadata.

The idea for workflows is to allow people to search commands based on what they accomplish, rather than requiring everybody to remember the command and type. For example, if I wanted to delete all empty files in a line, instead of remembering the exact incantation of sed to accomplish this, I could search "delete empty files".

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

#512

Post by girvo »

Arcuru wrote: post #457
ddoolin wrote: post #251

Earlier quoted context omitted.

This is why I deleted Fig ( https://fig.io/ ) right after installing it. It must've sent some uninstall information, too, because the creator/CEO emailed asking why I uninstalled it afterwards...

Oh yea, Fig is also the one that is Mac only but never mentions that fact anywhere on their website. Everything is written to just presume that the reader is on a Mac. Their getting started instructions [0] are all just terminal commands too, and even that doesn't mention Mac once. [0] - https://fig.io/docs/getting-started

> Oh yea, Fig is also the one that is Mac only but never mentions that fact anywhere on their website. Everything is written to just presume that the reader is on a Mac.

Not that it is not annoying, it is, but that's pretty common with Mac-only software in my experience.

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

#513

Post by girvo »

zachlloyd wrote: post #302
stormbrew wrote: post #205

Earlier quoted context omitted.

It's just.. an incredibly bad look to have this be the top comment on a post about this while the website claims that "cloud stuff" is opt-in. It's more essential to be honest about this during the beta period than after, so "oh it will be opt in" is a cold comfort, alongside the approximately never-true "we'll open source it some day." Not touching this with a ten foot pole. Not for something as essential to my day…

We tried to be really upfront in the privacy policy: https://www.warp.dev/privacy Opt-in refers to anything that sends any contents of a terminal session to our servers (as opposed to telemetry which is metadata and never contains any terminal input or output). But we hear the feedback and appreciate it.

Wrong crowd for this approach, I think.

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

#514

Post by losvedir »

As someone who uses the terminal a lot and is not allergic to closed source tools or even telemetry necessarily, I'd be in your target market, I think.

But one thing that your landing page has left me confused about: you have two examples like this:

    cargo +stable fmt
    cargo +stable check
    cargo +stable tests/
presumably to show off multi-cursors. But in neither example does the person appear to hit "Enter", which is the part I'm really wondering about. Like... what happens? If you run three separate commands like that at the same time are they in separate subshells or implicitly `&&`'ed together or something else? What's the return status if either `check` or `tests` fails? If `check` fails but `tests` pass... is the check failure's exit status lost? What does (e.g. in fish) `echo $status` say afterwards?

Multi-cursors and multi-line editing is definitely cool, but the example there totally doesn't match my mental model of a how a shell works, so it leaves me perplexed and confused how warp actually works.

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

#515

Post by cieplik »

kzrdude wrote: post #474
metadat wrote: post #382

"We started with the open source product Alacritty, though for now we won't be sharing our source code. ..But depending on the telemetry we receive we might decide to make the source available at some undetermined point in the future! Maybe." Talk about a bad taste. This is basically the Elasticsearch licensing fiasco waiting to happen again. So many red flags, I don't have time to list them. Bottom line: The company…

Why the bad taste? If Alacritty doesn't want to be close-forked they should use a copyleft license.

It's also worth mentioning that we didn't "just copy" Alacritty. We actually collaborated with Alacritty creators when starting Warp.

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

#516

Post by atonse »

zhengt wrote: post #423
atonse wrote: 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…

I actually have no issue with free/paid. It’s the login requirement that’s bothering me. But you’re saying that’s the part that’s used by telemetry?

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

#517

Post by skoskie »

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?

In production, agreed. In beta, I’ll accept it. I feel that the term beta gets abused a lot, but in what I believe is it’s proper meaning, there are a lot of inherent factors both parties are agreeing to; increased risk of error and data loss, and debugging flags that generate more data for the singular purpose of improving the product. That’s exactly what should be in the privacy policy and explicitly stated upon install. Anything short of that puts me firmly in the hell-no category with you.

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

#519

Post by zhengt »

varenc wrote: post #493
nlh wrote: post #462

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…

There's an active Discord with 700+ Warp users. I reported issues on it and immediately got helpful replies. They're talking to lots of real-world users. My take is that the hacker news crowd is not the target market for Warp. I think it does an amazing job of making the terminal easy and friendly to infrequent users. I'd recommend it to anyone who tells me they prefer a git GUI interface over the shell because of ho…

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.

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

#520

Post by dicknuckle »

michlim wrote: post #202
JoBrad wrote: post #120

Earlier quoted context omitted.

Do you track input during beta?

No, we do not track console input or output. Just metadata like: "block copied", "block selected", "bootstrapping failed". For an exhaustive list of events and metadata we collect, see: https://docs.warp.dev/getting-started/privacy#exhaustive-tel...

We're too lazy to read over that list. Bye.
Post reply on HN