I would never use a cloud-syncing cloud-connected terminal for simple security and privacy reasons alone, not to mention the fact that if it goes down I become basically disabled as a developer or admin.
Several companies have tried to SaaSify the terminal and failed, so I suspect I am not alone here.
"We've noticed that there's a component of the computing infrastructure that isn't sending everything you do to the cloud and charging monthly rent..."
Yes I'm genuinely shocked at the other comments here saying they use this happily; it should be a cause for concern. That it's now landing in Amazon's lap, doubly so.
> All cloud features are opt-in and your data is encrypted at rest. For autocomplete, all of your keystrokes are processed locally and never leave your device.
If Fig goes down, you fall back to the regular shell that doesn't have autocomplete etc. If Fig gets hacked, that's scary, then again GitHub and others are similarly big targets.
Idk though, this doesn't seem useful enough to me as an individual that I'd bother looking into it. Maybe for a team or company.
As a side note, if your security relies on you typing things into your terminal, you're doing it wrong. AWS even makes you check a box when generating creds that basically says "I understand the way I'm doing this is insecure" when generating creds that will be used that way.
I would use this as the way for company's command line tools to be provisioned to me as a team member. This means my tools can be separated from work tools
Several companies have tried to SaaSify the terminal and failed, so I suspect I am not alone here.
"We've noticed that there's a component of the computing infrastructure that isn't sending everything you do to the cloud and charging monthly rent..."