alokedesai
Joined 12 years ago
Karma
939
Submissions
91
Member since
Feb 12
Recent submissions
Comment · 6 months ago
Comment · 6 months ago
Appreciate the kind words!
Comment · 6 months ago
Warp is still a terminal, but it also has a coding agent.
no requirement to use it--and you can turn off all of the AI features if you don't want to use them at all
Comment · 6 months ago
Awesome to hear that the features are reasonating with you, thanks for the kind words!
Comment · 6 months ago
Hey, Aloke from Warp here.
We've actually added a ton of controls recently to let users configure how much (or little) UI they want. If that's not enough, would love if you opened an issue on the Warp repo and we can discuss more what needs to change in the product to meet your needs!
Comment · 1 year ago
Thank you for the kind words!
Comment · 1 year ago
Hey there, this is Aloke from Warp here. We originally built custom tab completions in Warp partly because of limitations with how Warp’s input works. We think our completions can be better for a lot of common commands (git, yarn, npm, etc) but I totally hear you that when completions in Warp don’t work like they do in another terminal it’s very frustrating.
No ETA for this yet, but this is very much on our radar to fix asap.
Comment · 1 year ago
Aloke from Warp here. The experience if you don’t have admin access isn’t great—I’ll follow up and make sure this gets fixed.
Comment · 2 years ago
Hi! I’m Aloke, an engineer at Warp.
I’m really excited to share that Warp is now available on Linux! If you’re interested in trying it out, you can download Warp at https://www.warp.dev/.
We've gotten 2-3 reports of authentication issues like the one the author mentions. We are actively looking into it; we believe its an issue with a library we depend on to open URLs. If anyone is experiencing these issues, please contact us at [email protected] so we can better understand the issue and further debug!
Building Warp on Linux was quite an undertaking. Warp uses a custom Rust-based UI framework that we built in house and renders natively on the GPU. To get Warp running on Linux, we built a version of our UI framework that supports winit [1] as a windowing backend. We also built a version of our renderer that uses wgpu [2]. Reducing complexity by using these well-supported, cross platform, frameworks let us bootstrap a version of Linux quicker than expected and should make it easier to build Warp for other platforms (like Windows).
Please let me know what you think! Happy to answer any questions, either about the product or about technical challenges.
[1] https://github.com/rust-windowing/winit [2] https://github.com/gfx-rs/wgpu
Comment · 2 years ago
Hi! I’m Aloke, an engineer at Warp.
I’m really excited to share that Warp is now available on Linux! If you’re interested in trying it out, you can download Warp: https://warp.dev/
Building Warp on Linux was quite an undertaking. Warp uses a custom Rust-based UI framework that we built in house and renders natively on the GPU. To get Warp running on Linux, we built a version of our UI framework that supports winit [1] as a windowing backend. We also built a version of our renderer that uses wgpu [2]. Reducing complexity by using these well-supported, cross platform, frameworks let us bootstrap a version of Linux quicker than expected and should make it easier to build Warp for other platforms (like Windows).
Please let me know what you think! Happy to answer any questions, either about the product or about technical challenges.
[1] https://github.com/rust-windowing/winit [2] https://github.com/gfx-rs/wgpu
Comment · 3 years ago
Hey there, thanks for feedback. We built our own UI framework in Rust to build Warp, and there were some initial rendering quirks--especially with rendering text on low resolution monitors.
I'd love to hear more about the rendering issues you've faced when using Warp so we can fix them!
Comment · 3 years ago
Hey there, engineer from Warp here. Warp never collects input or output from the console. There is only high-level tracking for monitoring app crashes and some feature usage data. Our philosophy is total transparency around telemetry. We’ve created a Network Log tool you can use to watch all events in real-time [1] and we have a full list of telemetry events we record in Warp’s docs [2]. You can also opt out of telemetry in Warp’s settings.
Warp requires a login to support its collaboration features (for example sharing commands with a team). Login makes it possible for developers to collaborate securely.
[1] https://docs.warp.dev/features/network-log [2] https://docs.warp.dev/getting-started/privacy#exhaustive-tel...
To add more color to some of your points in the post above:
* We give users the option to disable telemetry before sending any back to our servers.
* We use Sentry for crash reporting, this can be disabled.
* Yes, we record telemetry with the option to disable. The events are in our source code (as you point out) and also on our website.
* We have a network log in app that you can open and view _any_ request we make, including requests to send telemetry.
* If you compile the OSS build it has no telemetry or crash reporting.
Our motivation with open sourcing is to build more trust with our community, not less. Happy to discuss more and, of course, the codebase is available to audit.