571–580 of 757 posts
Earlier quoted context omitted.
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?
Right now, login is required while we're in Open Beta. When we GA, login will be opt-in (although you'd lose some of our cooler features).
Like others here, I'm leery of replacing my terminal with a VC-backed, maybe open-sourced eventually product, and a bit annoyed it claimed a name already in use in the Rust world. But...it is exciting to see someone reimagining the terminal a bit. People frequently talk about wanting a better GUI interaction model for everyone, but the actual ideas to improve it seem to be missing, I think because the desktop status…
In order to promote the idea I've been spending most of the time writing a client in Go. I think it has enough functionality that I can start writing servers that really showcase the capabilities.
I want to like this, and clearly a lot of work went into it, but the existing tooling here has gotten so good lately, without losing any of the power user affordances. WezTerm is crazy fast with GPU-accelerated ligatures, mcfly has an NN in it that startles me, fzf, rg, bat. Everything has bash/zag/fish autocomplete in it now. tmux customization has become a high art form, VSCode has forced all the best language tool…
It’s on a visibility toggle with one key, nice margins on all sides, tmux, spaceship prompt, a color scheme that matches my IDE, I can hide the title bar if I like. It’s basically perfect. I don’t need error messages with rounded borders.
It looks nice but I'd never use a shell that phone's home. Period. I 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.
Regarding the other thoughts in this post, I have to agree. I use iTerm instead of Terminal.app, but if I had even the remotest fear that it was sending anything elsewhere, I would jump ship. My terminal has all kinds of information that can act on my behalf, and I wouldn't want any of it leaving my Mac at all, ever, period. Had this been open-ish source but not phoned home, I'd give it a try. But opaque data leaving for who knows where? Nope.
Earlier quoted context omitted.
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.
> We are actively working on a11y! Glad to hear it! I'm working on a Rust GUI accessibility library that might interest you: https://github.com/AccessKit/accesskit If you'd like to email me so we can compare implementation approaches and perhaps avoid duplicated effort, my email address is in my HN profile.
Everything you'd want to do in a terminal that is worth sharing would be version controlled, which is vastly superior in everyway.
You've all done some cool work here, and I can complement that, but I think this is a really weird idea with no real world evidence to justify its existence.
There are some legitimate concerns about Warp throughout these comments (telemetry, business model, etc.). But 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 fun…
It's nice to think of this as 'taking advantage of' VC dollars, but VC dollars come with strings attached, namely the need for an 'exit'. The exit only happens if the company in question makes multiples of what it invested, meaning that VC-funded companies need significant revenue from their users. These days, the growth required for an exit leads to: 1) advertising being laced into a product, 2) user data being sold or otherwise monetized, or 3) charging you a monthly subscription fee.
Maybe this time it's different—there are theoretically other VC-friendly business models that work for software—but I struggle to see how.
Open-sourcing the application from the beginning would certainly give more confidence here.
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…
what is it to talk about? Anything to be discussed about telemetry as a general concept, has been discussed in other products at some point. I personally think the paranoid toward telemetry is just an ideological one, I doubt people can articulate exactly how telemetry is detrimental to them. I would not blame companies for adding telemetry for improving their product (instead of tracking user), and not explicitly te…
It’s not hard to articulate. Here’s Der Spiegel’s 2013 reporting on the NSA’s use of Windows telemetry for passive observation of targets:
> The automated crash reports are a "neat way" to gain "passive access" to a machine, … [this] provides valuable insights into problems with a targeted person's computer and, thus, information on security holes that might be exploitable for planting malware or spyware on the unwitting victim's computer.
> In one internal graphic, [the NSA] replaced the text of Microsoft's original error message with one of their own reading, "This information may be intercepted by a foreign sigint system to gather detailed information and better exploit your machine."
Earlier quoted context omitted.
Exactly, that's why people tend not to choose Windows for development unless they're forced to. edit: use -> choose
> Exactly, that's why people tend not to choose Windows for development unless they're forced to. In my experience, most people who are developing software for Windows choose to use it to develop that software. There are a great many people who choose to develop software for Windows.
But I choose not to.
Earlier quoted context omitted.
Agree, this is a pretty bad deal breaker for me. Big business people doing short-sighted big business things, salivating at cramming a product full of telemetry. All without transparency around it? In a terminal of all things?? Indescribably off-putting and catastrophically damages my trust in the product and the CEO. EDIT: To be fair there is some transparency in the original post. I was looking through the landing…
Hi - as the poster and founder I again completely get the concern. We should make it even more transparent what we collect. You can see it here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... Re: big business, we're still pretty small, but it's true that we are trying to build a business around the command-line. I get that's controversial and it's not something that exists and that the terminal is a…
Given that, it's probably the case that the only options are to either be fully open source or to make a fully offline mode an option.
In any case, I think the concept for your product is excellent—it's been mind-boggling to me that something along these lines wasn't tackled years ago, so I look forward to your guys' future success, hopefully moving the state of terminal interaction into the modern era.