201–210 of 757 posts
Earlier quoted context omitted.
they’ll have a business offering which lets people collaborate
If collaboration is the angle, JetBrains and VSCode already offer that but without forcing people to use specific terminals.
Earlier quoted context omitted.
Warp engineer here. I understand your concern. We will remove telemetry when we enter general availability. It will be opt-in and anonymous. We really want to improve the product quickly during this beta phase. Collecting data makes it much easier to reach out and get feedback when something goes wrong. But we only track metadata, never console output. For an exhaustive list of events that we track, see here: https:/…
Do you track input during beta?
For an exhaustive list of events and metadata we collect, see: https://docs.warp.dev/getting-started/privacy#exhaustive-tel...
That's a shame because terminal multiplexers like GNU screen and tmux such a core part of my terminal usage that I'm hesitant to discard them, even for something that looks really useful like Warp.
I'm not sure how many people actively use terminal multiplexers like GNU screen and tmux, so maybe I represent only a tiny minority of users.
Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
It's more essential to be honest about this during the beta period than after, so "oh it will be opt in" is a cold comfort, alongside the approximately never-true "we'll open source it some day."
Not touching this with a ten foot pole. Not for something as essential to my day to day work as a terminal.
Earlier quoted context omitted.
I'm not sure I'm ready to have SaaS models replace core utilities and tools locally. > Announcing Warp’s Series A: $17M to build a better terminal And just thinking about this... it's not clear to me what their moat will be as I suspect if there's a really compelling feature it will be available in OSS terminals quite quickly. Perhaps it's the product polish? But I'm not sure polish is what I want from a terminal, at…
Warp engineer here. 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 - Sessi…
> - Wikis and READMEs that run directly in the terminal No thank you
> - Session sharing for joint debugging = That's more for development.. not for shell access
> 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.
I actually don't want them. I migrated from many apps that do too much to apps that do one thing really well.
Earlier quoted context omitted.
Warp engineer here. I understand your concern. We will remove telemetry when we enter general availability. It will be opt-in and anonymous. We really want to improve the product quickly during this beta phase. Collecting data makes it much easier to reach out and get feedback when something goes wrong. But we only track metadata, never console output. For an exhaustive list of events that we track, see here: https:/…
This type of canned response doesn't sit well with me. Keep us posted when you're out of beta and those things are removed, do you have a timeline for that?
Earlier quoted context omitted.
I definitely understand the concerns. For our public beta, we do send telemetry and associate it with the logged in user because it makes it much easier to reach out and get feedback when something goes wrong. But we only track metadata, never console output. For an exhaustive list of events that we track, see here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... . Once we hit general availability, ou…
Maybe don't put this lie in the middle of the homepage? > Private & Secure > All cloud features are opt-in. Data is encrypted at rest.
Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
Yup, well, that's what happens when you take money from VCs or other third party investors, you need to monetise / demonstrate ROI / need numbers for your investor slide-decks.
I'll stick to my old-fashioned spyware free terminal thanks very much. Why overcomplicate things that don't need to be complicated.
Earlier quoted context omitted.
I'm not sure I'm ready to have SaaS models replace core utilities and tools locally. > Announcing Warp’s Series A: $17M to build a better terminal And just thinking about this... it's not clear to me what their moat will be as I suspect if there's a really compelling feature it will be available in OSS terminals quite quickly. Perhaps it's the product polish? But I'm not sure polish is what I want from a terminal, at…
I doubt their compelling features will be in OSS terminals any time soon. I’ve wanted a terminal that has a decent multi line editor for years , and there’s nothing out there.
Most of the stuff sibling comment is referring to center around the feature:
'edit-and-execute-command' in bash. There is a similar incantation for zsh.
I summon it with, 'ESC v' in both.