I like what they are doing. And like copilot (which I'm not a fan of, but I understand the goal maybe), I think it is leaning toward the real issue - we waste energy solving the same problems over and over.
Instead of helpers which enable us to reinvent wheels, we should be directing our efforts toward establishing a collection of pattern solutions and tools to compose those solutions into bigger ones which solve specific needs.
In the terminal, there are certainly a limited set of things we do repeatedly. In fact, much of what we do in the terminal can be done elsewhere (UI); it's just slower or more tedious due to clicking. It's also less easy to automate. But the intentions behind the actions are the same. "Create a new directory <here> name <name> and execute this <script>". Perhaps the biggest challenge is just in naming and organizing.
That's an interesting point you raise - definitely agree that there's tons of wasted efforts solving the same problems multiple times. With Warp, the eventual hope is to build an ecosystem for developers to be able to collaborate with each other and build reusable extensions directly on top of the terminal, to help address the concerns you mentioned.
Though, fostering this environment for collaboration can be quite difficult - in your experiences, what do you think would work well for creating such an ecosystem, where we can prevent duplicative work and encourage sharing?
But how to identify common patterns of problems? I think we just need to make an effort to zoom out and consider the phases of software development and infrastructure management we do, then look for similarities.
For example on the web development side, we routinely build web application foundations which require authentication (and less often but also authorization), state storage (database backends), and presentation layers. And yet, unless you start with something like Wordpress, there is little out there which provides a fundamental foundation with modular extensibility.
From a terminal perspective, we manage processes - start/pause/kill, we check states - active network connections, running processes, resource consumption levels, and we do ad-hoc data processing (piped unix commands, but typically in service of one of the previous two categories of needs).
In my work, I commonly use tmux to keep sessions open for different constant needs like psql shell, tail -f of logs, and other routine system management tasks. Most of these could be modules enabled and configured within a management system. I'm sure plenty of other people here have built their own scripts to do exactly this, especially for text or tiled UI systems.
Moving on.
Just wanted to clarify that Warp is completely free for single users :)
And in terms of telemetry, Warp never sends the contents of terminal commands and outputs to our servers (unless a user explicitly chooses to use the "Block Sharing" feature). What Warp currently sends in regard to telemetry is listed here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel...
Hope that helps!
Also most of the capable sysadmins and CLI junkies that I know use Linux. Not supporting that first is a strange choice.
As cool as this idea is, I feel the only way I could ever responsibly have it is by ripping it off and actually making it open and available to all platforms.
Nope.
Nope
