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

51–60 of 757 posts

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

#51

Post by jacobsimon »

orastor wrote: 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…

Come on. You must realize VS Code and basically every website you use collects telemetry data, which is rarely for anything nefarious except product improvements. If GitHub/Microsoft had released this product, would you be raising the same concerns?

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

#52

Post by blktiger »

alokedesai wrote: post #30
orastor wrote: 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…

I definitely understand the concerns. For our public beta, we do send telemetry and 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 output. For an exhaustive list of events that we track, see here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... . Once we hit general availability, ou…

I definitely will not try it if the analytics part are not optional, though I am glad to see you're documenting exactly what gets sent. I might consider trying it and even opt-in to the analytics once you make it optional.

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

#53

Post by ritmatter »

Excited to see this launch! I think there is a lot of opportunity for a terminal that is aware of the fact that the one-computer-per-dev model is not really how it works anymore. That, and a terminal that can help me avoid big mistakes, help me remember commands, and more. It's great to see innovation take place in this space.

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

#54

Post by qbasic_forever »

orastor wrote: 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…

Wait, you _have_ to have a github account to even open this terminal?

Yikes.

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

#55

Post by exdsq »

jacobsimon wrote: post #51
orastor wrote: 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…

Come on. You must realize VS Code and basically every website you use collects telemetry data, which is rarely for anything nefarious except product improvements. If GitHub/Microsoft had released this product, would you be raising the same concerns?

Maybe not but I'd trust Microsoft has a decent security and privacy team working on this more than a startup. What if they're logging the wrong stuff and my data is leaked?

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

#57

Post by varbhat »

I use configured zsh which has majority of features mentioned above. It is integrated with fzf and also has autcompletions(with help description), autosuggestions,hints, file completions and more. You can see my zsh dotfiles below.

https://github.com/varbhat/dotfiles/tree/main/dot_config/zsh

I could even have enabled real time type ahead completions with this plugin but i haven't (because i don't need this feature) : https://github.com/marlonrichert/zsh-autocomplete

i use my current configuration on foot terminal (which itself is blazing fast and boasts fastest vtt parser) in linux and kitty terminal (which is very feature rich, even has terminal graphics protocol so that you can even run glxgears(opengl cube demo: https://github.com/michaeljclark/glkitty) on it) on linux and macos.

i am sure that other shells such has fish also have these features.

So, what benefits do i get on switching to warp? currently,i don't see any except few marketing words which aren't enough for me to start using warp.

I might be missing something but i am all ears.

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

#58

Post by kitsunesoba »

One feature that’s missing from a surprising number of Mac terminals is a hotkey-bound non-activating dropdown (think Quake console) or HUD window (imagine a floating, frameless terminal window in the vein of the Alfred or Spotlight window).

The best implementation of this to date was in TotalTerminal/Visor, which was a mod for the Apple terminal that added this feature but naturally went the way of the dodo when macOS added SIP. iTerm2 has a feature that kinda does this, but that implementation is comparatively janky and half-baked feeling.

If Warp gained a polished version of this there’s a good chance of it becoming a mainstay on my systems.

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

#59

Post by michlim »

munro wrote: post #35

> Telemetry > When Warp comes out of beta, telemetry will be opt-in and anonymous. > But for our beta phase, we do send telemetry by default 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. This is a hard pass for me, it looks really amazing though. I'm so tired of telemetry, how do we quit our day jobs to focus on open source? ;-;

Warp engineer here. I understand your concern.

We will remove telemetry when we enter general availability. It will be opt-in and anonymous.

We really want to improve the product quickly during this beta phase. Collecting data makes it much easier to reach out and get feedback when something goes wrong. But we only track metadata, never console output. For an exhaustive list of events that we track, see here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel....

We are going to open source parts and potentially all of the terminal. We want to allow folks to audit our code and tweak Warp.

Post reply on HN