Warp is a fast, Rust-based terminal. Key features include:
1. Modern editor that lets you edit input like an IDE
2. Input and output are grouped in blocks for easier navigation
3. Integrated AI for command suggestions, debugging, and chat
4. "Warp Drive" to save parameterized commands as reusable workflows (like aliases but easier to use and more powerful)
> With this strategy, GC pre-funds a company’s S&M budget. In return, GC is entitled only to the customer value created by that spend, and GC’s entitlement is capped at a fixed amount. After GC reaches that fixed amount, the remaining lifetime value of the customers is the company’s to keep forever.
Good to see more ways of growing without giving up equity.
tldr; My teammate solved a bug by finding a detailed commit message in Chromium’s repo. High-quality git commits are an underrated form of documentation.
I like the concrete advice here on how to navigate distrust:
1. Lead with your bias.
2. Avoid cheap shots.
3. Be your own biggest critic.
4. You can still talk shit about software, just not your competitors‘ software.
5. Be generous with your expertise.
I agree with this take. Moreover, it takes a seasoned software architect to verify that the code generated is correct, clean, and idiomatic. Someone still needs to shepherd the machine.
> There's actually a growing body of evidence that shows the emergent ability of LLMs to reason (the so-called "chain of thought" ability) arises only when LLMs are trained on huge amounts of code, not just natural language. Natural language training data provides the ability to sound human, but it is the programming language training data that provides LLMs with the ability to be logical.
Good on Sourcegraph to contribute back to the open source community. LLMs rely more on open source code than meets the eye.
We do want to support linux once we get the product experience right. We decided to build in Rust and set up a UI framework because we wanted to make it easier for us to port to Linux.
For now, every platform we support entails additional engineering overhead that takes away from getting to product-market fit. Once there, we will invest resources into supporting Linux, Windows, and the Web.
Warp engineer here. Really appreciate your ideas here!
> Warp's more visual completion is super welcome. Does it work with the shell's standard completion scripts?
It does not. But we have completions out of the box for 200 commands.
Warp's input is a text editor instead of the shell input. This means we ended up building completions by hand and soon, via the community. We think this is a better experience because we can provide more in-line documentation.
> Warp's blocks look like a nice step in the right direction. How do they work?
tldr; shell hooks
Most shells provide hooks for before the prompt is rendered (zsh calls this precmd) and before a command is executed (preexec). Using these hooks, we send a custom Device Control String (DCS) from the running session to Warp. Our DCS contains an encoded JSON string that includes metadata about the session that we want to render. Within Warp we can parse the DCS, deserialize the JSON, and create a new block within our data model.
Re: impersonation: that's a good concern we will consider.
> It'd be interesting to further extend blocks with some protocol that allows programs to output within their block using richer elements.
Absolutely! This is definitely in the roadmap. We want rich output like adjustable tables and images. We also want to support a protocol so other CLI programs can use it.
> Likewise, when launching alternate-screen terminal stuff, to allow them to do more with the rectangle than a grid of text.
Yes we are thinking of supporting blocks within tmux, for example.
> And at first glance, looks like it's missing tmux-like features (whether integration with tmux proper like iTerm has or its own thing).
Yes, other than split panes, we do not have tmux-like features. We've begun mocking out what those features could look like. We are thinking of a native window management solution and a native way of saving workspace/session templates.
We are also thinking of what a deeper integration with Tmux might look like.
FWIW, the Warp terminal will be free for individuals. We would never charge for anything a terminal currently does. So no paywalls around SSH or anything like that. The types of features we could eventually charge for are team features.
Our bet is that the moat is going to be the team features, like:
- Sharing hard-to-remember workflows
- Wikis and READMEs that run directly in the terminal
- Session sharing for joint debugging
Our bet is their companies are willing to pay for these. BTW, even these team features will likely be free up to some level of usage and only charged in a company context.
The terminal is totally free for individuals. Our business model is to make the terminal so useful for individuals that their companies will want to pay for the team features.
We will not degrade your experience: we would never charge for anything a terminal currently does. No paywalls around SSH or features that don't cost us money. We will never sell your data. We treat privacy seriously at Warp: check out www.warp.dev/privacy for more information.
We are planning to open-source parts and potentially all of the terminal.
Building a terminal is hard. We have to build feature parity, maintain a stable terminal-shell interface, on top of modernizing the product experience. The money allows us to hire engineers to work on this project full-time and create a great product experience.
Warp is a fast, Rust-based terminal. Key features include: 1. Modern editor that lets you edit input like an IDE 2. Input and output are grouped in blocks for easier navigation 3. Integrated AI for command suggestions, debugging, and chat 4. "Warp Drive" to save parameterized commands as reusable workflows (like aliases but easier to use and more powerful)