Before I would ever even think about adopting this tool commercially, especially considering the massive leverage a it has over such a critical piece of business infrastructure, I'd require them to offer some very serious, verifiable, and continuous guarantees about their security setup (the current "your privacy is important to us" doesn't really cut it) and legally binding guarantees to cover for the remaining liabilities.
At that point I'm afraid the SLA would be so expensive it wouldn't be worth the investment.
It's brutal, I know, but a nice looking terminal app just isn't worth risking my customers' and my own arses over š
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I totally agree. I just don't see the draw of any software that's not free, especially when it offers so little over established free software.
I'm going to come out with a whole lot of things that sound negative, but I don't mean, "I hate this, stop what you're doing", I mean, "I don't understand this, carry on and make something awesome".
It seems like the only thing that Warp gives you beyond other terminals so far is workflows, which look quite nifty tbh, but - and it's a big but - I don't think they'd be difficult to implement as a script in any old shell, even something 20+ years old that's supported by curses. I can think of a few people from my work who'd probably like the feature
Phrases like "planning on open sourcing some of the..." turn me off. Why would parts of it be hidden? Why is this a thought for the future and not how it's built from the start?
I'm also dubious of new software that's built for MacOS where the authors say they're working on versions for other OS. The reason that people choose to build for Mac first is often that they can charge more for the product and people will pay it, and as such the other platforms' versions fail to materialise or are always a step behind if they do.
I'm not sure that things like command history and workflows are a good fit for a terminal emulator. I think they're a fit for the shell, because the shell's the thing that is interpreting them. You can use a terminal emulator to run something other than a shell, and in that case, what's it going to do? Will the shortcut keys confuse things?
A lot of these questions are definitely for the warp team, which Iām not a part of.
The software is free to use and nothing restricts you and your whole team from using it. Their business model is go for mass adoption, then hope to offer business and companies X or Y where a free tier would have a restricted version (as far as I can tell)
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
While I agree with some sentiment here, this has been discussed openly:
github.com/warpdotdev/Warp/discuss...
Seems they are planning on open sourcing some if not all of the terminal.
That would be the baseline for personal use.
Before I would ever even think about adopting this tool commercially, especially considering the massive leverage a it has over such a critical piece of business infrastructure, I'd require them to offer some very serious, verifiable, and continuous guarantees about their security setup (the current "your privacy is important to us" doesn't really cut it) and legally binding guarantees to cover for the remaining liabilities.
At that point I'm afraid the SLA would be so expensive it wouldn't be worth the investment.
It's brutal, I know, but a nice looking terminal app just isn't worth risking my customers' and my own arses over š
I totally agree. I just don't see the draw of any software that's not free, especially when it offers so little over established free software.
I'm going to come out with a whole lot of things that sound negative, but I don't mean, "I hate this, stop what you're doing", I mean, "I don't understand this, carry on and make something awesome".
It seems like the only thing that Warp gives you beyond other terminals so far is workflows, which look quite nifty tbh, but - and it's a big but - I don't think they'd be difficult to implement as a script in any old shell, even something 20+ years old that's supported by curses. I can think of a few people from my work who'd probably like the feature
Phrases like "planning on open sourcing some of the..." turn me off. Why would parts of it be hidden? Why is this a thought for the future and not how it's built from the start?
I'm also dubious of new software that's built for MacOS where the authors say they're working on versions for other OS. The reason that people choose to build for Mac first is often that they can charge more for the product and people will pay it, and as such the other platforms' versions fail to materialise or are always a step behind if they do.
I'm not sure that things like command history and workflows are a good fit for a terminal emulator. I think they're a fit for the shell, because the shell's the thing that is interpreting them. You can use a terminal emulator to run something other than a shell, and in that case, what's it going to do? Will the shortcut keys confuse things?
A lot of these questions are definitely for the warp team, which Iām not a part of.
The software is free to use and nothing restricts you and your whole team from using it. Their business model is go for mass adoption, then hope to offer business and companies X or Y where a free tier would have a restricted version (as far as I can tell)