4 ms·
About time. More startups should realize that they could increase developer adoption of their products if also published shell script interfaces to their produ
by unono 13y ago
About time.
More startups should realize that they could increase developer adoption of their products if also published shell script interfaces to their product. In fact, your startup should really start off as command line accessible and add the gui after.
- rrrhys 13y ago"start off as command line accessible and add the gui after" As much as I'd love this to be true, it is so wrong unless you are targeting other very technical users. Most people I know (ie, potential customers) think anything in the command line is old/impossible to use/nerdy.
- thex86 13y agoRight, in this case it actually makes sense because you will already be technically proficient if you are using something like AWS. But in other cases, the GUI can be the main interface, but a CLI to back it up is pretty awesome and I had happily pay some provider extra bucks for it.
- jeffbarr 13y agoI'm with you on this. As an "old" command line person (I first learned Unix in 1980 or so), I still tend to think of the GUI as an add-on.
- jeffbarr 13y agoThere have been CLI tools for some parts of AWS since the beginning. This release replaces a set of disparate tools (each with their own installation instructions and configuration issues) with a unified set. > In fact, your startup should really start off as command line accessible... I would argue that startups should always start at the API level and work upwards. At least that's what we did with AWS.
- MichaelGG 13y agoStarting off from the API seems like the only sensible way to approach things. It exposes core design issues early on, and if done right, eliminates a wide source of security issues that might be introduced by, say, the front-end developers.