| This is a enterprise product, and I can easily see how its adoption can save an organization a lot of time. Easily share out custom workflows to fetch development keys and login to different services. Onboarding scripts that setup all the terminal things needed for development environment. > "the obscene SaaSification of a basic foundational utility" Watching their demo vid, it is a very nice terminal that also supports org wide shared scripts, in a unified manner with autocomplete. Right now I have a text file with commands that I copy and paste daily to get things done. I share bits and pieces of this file with new hires when they onboard to solve various common problems. This shell solves that problem for an entire organization, and it does so in a discoverable way. Can an org have their own repo of shell scripts? Sure, but then you have to make sure all developers in the org pull the latest when changes happen, and discoverability within "folder full of scripts" isn't the best. > The fact that the telemetry code even exists is a problem - both in case of a bug that turns it on, and what it says about the proclivities of its developers. Telemetry exists because running user studies is expensive. "What features are people using, what is crashing, where are people getting frustrated". |