zachlloyd

8 ms·

31.
Why is the terminal input so weird?(warp.dev)
110 points by zachlloyd 4y ago|178 comments
32.
by zachlloyd 4y ago
Looking forward to it! Please tag me at twitter.com/zachlloydtweets - i'd love to read and respond
33.
by zachlloyd 4y ago
That's an interesting point regarding the costs of the client vs. the cloud, and also that you can get a more hermetic experience with local VMS. Agreed on the latency concern. Thanks for the feedback!
34.
Why is it taking so long for cloud dev environments to catch on?(warp.dev)
8 points by zachlloyd 4y ago|8 comments
35.
Learnings from interning on a Rust-based terminal(warp.dev)
10 points by zachlloyd 4y ago|0 comments
36.
Adventures in Text Rendering: Kerning and Glyph Atlases(warp.dev)
61 points by zachlloyd 4y ago|17 comments
37.
“Why you should join”: new Stanford student newsletter (feat Warp.dev)(whyyoushouldjoin.substack.com)
5 points by zachlloyd 4y ago|0 comments
38.
The Google incentive mismatch: Problems with promotion-oriented cultures(warp.dev)
634 points by zachlloyd 4y ago|591 comments
39.
by zachlloyd 5y ago
We spoke with a lot of users (someone mentioned our discord which has thousands of members) and there are thousands of developers using Warp every day (prior to this ShowHN). We also were expecting some of this response from the HN communit
40.
by zachlloyd 5y ago
For sure - one of my main takeaways from our ShowHN is that there's a ton of reasonable concern around login, telemetry, and open source that we need to address. We are going to come back to HN as we do that. The HN community has a di
41.
by zachlloyd 5y ago
Thanks for the feedback - I'm the founder at Warp. There was a ton of discussion on this yesterday with our ShowHN [0] and we are considering what changes to make based on the feedback (some of which are inline with your suggestions).
42.
by zachlloyd 5y ago
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
43.
by zachlloyd 5y ago
As the author of the post (and founder of the company), I think this is also a very reasonable concern. It's one that we have as well and that we take very seriously. Our stance here is that: 1) We are very explicit about what gets se
44.
by zachlloyd 5y ago
As the author of the post, I think this is totally reasonable feedback and something we have discussed quite a bit on the team. The general stance on telemetry that we have is that a) we are just starting and it's really helpful to see
45.
by zachlloyd 5y ago
Thanks for the positive feedback - let us know how it goes.
46.
by zachlloyd 5y ago
This is correct. We do not send or store any terminal contents (input or outputs) to our server. The only case in which that is not true is if a user elects to use Warp to share the output of a command using our Block Sharing feature.
47.
by zachlloyd 5y ago
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 c
48.
by zachlloyd 5y ago
I understand where you're coming from. My take is that there are plenty of commercial projects that have open source dependencies so it's not quite so black and white. That said we are still figuring out the best way to proceed o
49.
by zachlloyd 5y ago
it's a good question. today warp is a terminal as you say. the hope is that we can build a platform around the command-line, but we decided by trying to start with the terminal's fundamental UX to see if we could improve it. in
50.
by zachlloyd 5y ago
Thanks kyeb. I agree with both points here - we need to be very careful and sensitive in terms of how we build this product from a privacy and security perspective, but we see the opportunity mostly the same way you do. There are some grea
51.
by zachlloyd 5y ago
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 n
52.
Show HN: Warp, a Rust-based terminal(warp.dev)
946 points by zachlloyd 5y ago|726 comments
53.
by zachlloyd 5y ago
yup, i messed this up, apologies. site is handling the traffic better now thanks to cloudflare
54.
by zachlloyd 5y ago
i do agree
55.
by zachlloyd 5y ago
i see the point here. i do think giving space for hard work is important. i still more often see the opposite problem of too much silo'd work leads to wasted effort, but for some really hard problems, having a bunch of space to think
56.
by zachlloyd 5y ago
Right, we do a standup, but if you're not careful the updates can be generic enough like "making progress on X" where you still end up working too long without feedback
57.
by zachlloyd 5y ago
working on the issue with the site going down. more traffic than i expected...
58.
by zachlloyd 5y ago
Correct! IC == individual contributor. Sorry for any confusion
59.
by zachlloyd 5y ago
I'm the author of the post - would love any feedback / similar experiences / contrasting opinions!
60.
by zachlloyd 5y ago
Hi! I'm the author of the post. Glad folks found it interesting. One comment I would add on top of what's being discussed here is that I actually am not arguing that the main engineering tradeoff is between quality and speed. In

More ›