Show HN: Warp, a Rust-based terminal
131–140 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#132But the one thing that really excites me is to have a full team working full-time on building the terminal that developers want to use. They're doing real user research, talking to developers, and taking feedback in forums like HN seriously - and using up millions of VC-dollars building a new version of this fundamentally important core utility. I'd much rather have that VC money go toward an attempt at a better terminal than some ML or web3 startup.
I think this doesn't usually happen? All the terminal emulators I've used usually open-source projects developed in someone's free time. Don't get me wrong, projects like Alacritty, urxvt, xterm, Terminator etc. are amazing for the funding they have (I think mostly $0?), but I'm super excited to see what a cohesive terminal based on real UX research can look like.
Re: Show HN: Warp, a Rust-based terminal
#133I mean the CLI has been one of the last parts of my system that I really still trust is working on my behalf only.
This product made me rethink that assumption.
As for capturing the output from a command line on the mac (and also on linux IIRC) just use pbcopy/pbpaste.
My opinion: It's not worth giving your privacy away for features like this.
Re: Show HN: Warp, a Rust-based terminal
#134Re: Show HN: Warp, a Rust-based terminal
#135Re: Show HN: Warp, a Rust-based terminal
#136Why is a company building a terminal? How are they going to earn money at all when there are other fast, performant terminals that are open source, community run, and don't have interests at-odds with user freedom and privacy?
It seems like just about any tech project is being funded now.
edit: It's also sad that we're at the point of "no electron" being a selling point, when it should be the standard for CLI tools. And I'm so glad to see it supports other shells, like just about every other terminal out there.
Re: Show HN: Warp, a Rust-based terminal
#137Earlier quoted context omitted.
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…
This looks very interesting to me, but some of this telemetry is a deal breaker. On your privacy page, it says "Our general philosophy is complete transparency and control of any data leaving your machine." If I have complete control of any data leaving my machine, can I opt to turn off the telemetry entirely?
Re: Show HN: Warp, a Rust-based terminal
#138Re: Show HN: Warp, a Rust-based terminal
#139Wanted 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…
Re: Show HN: Warp, a Rust-based terminal
#140Earlier quoted context omitted.
> we only track metadata, never console output It would be meaningful to indicate whether you track console input as well.
That's an important callout! By console output, we really mean output from the pseudoterminal, which includes command input and output printed to the terminal. We don't store any content of _any_ part of a command that's executed in Warp.