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

61–70 of 757 posts

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

#61

Post by mritchie712 »

buro9 wrote: post #44
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'm not sure I'm ready to have SaaS models replace core utilities and tools locally. > Announcing Warp’s Series A: $17M to build a better terminal And just thinking about this... it's not clear to me what their moat will be as I suspect if there's a really compelling feature it will be available in OSS terminals quite quickly. Perhaps it's the product polish? But I'm not sure polish is what I want from a terminal, at…

The moat would be if teams depend on it for sharing workflows. Doing "teams" right on OSS is tricky, much easier to pull off in SaaS.

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

#62

Post by rubyist5eva »

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…

yeah I just block all of those domains in my dns reverse proxy now, idgaf

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

#63

Post by cieplik »

NoraCodes wrote: post #25
zachlloyd wrote: post #7

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

Is your framework well-integrated with accessibility tools on Mac OS? If so, will you continue to integrate with those tools on other platforms?

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.

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

#66

Post by progbits »

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…

Maybe don't put this lie in the middle of the homepage?

> Private & Secure

> All cloud features are opt-in. Data is encrypted at rest.

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

#67

Post by aorth »

Looks snazzy and I'm sure it's fast, but raising capital to fund a terminal emulator? Making a bunch of network requests on startup without asking? No thanks! I'll stick to open-source terminal emulators like foot, alacritty, gnome-terminal, or a dozen others. I guess I'm not the target market.

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

#68

Post by runako »

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…

> we only track metadata, never console output

It would be meaningful to indicate whether you track console input as well.

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

#70

Post by hbn »

NoraCodes wrote: post #40
hbn wrote: post #27

I've been loving Warp since discovering it on HN a few months back. I was originally drawn in by how it treats text input like a regular text input field out of the box, so I don't have to configure anything and my normal text editing shortcuts just work. But the other features of it have been really great too. I like the terminal splitting, the history searching, the command palette, and no performance issues I've n…

For what it's worth, if the keybindings you want are Vim or Emacs-like, you can get this behavior in Bash or Zsh (or probably other terminals) with literally one line of configuration.

I want it to behave like every other text input field on my Mac. So I can do option+left/right to jump words, Cmd+left/right to jump to beginning/end of a line, shift + move cursor to highlight text, Cmd+A to select all, option + forward delete to delete the whole word in front of my cursor, etc
Post reply on HN