3 ms·
Such verbosity (and other bloat and complexity in how AWS does things) is why I could never get excited about S3, EC2 et seq. when these services were first ann
by 1vuio0pswjnm7 5y ago
Such verbosity (and other bloat and complexity in how AWS does things) is why I could never get excited about S3, EC2 et seq. when these services were first announced. Rightly or wrongly, I believe it is because most of AWS was originally implemented in Java. Programming in Java requires a certain comfort with verbosity and clunkiness. That showed through in early AWS interfaces and documentation. Indeed, it has alway been painful to interact with manually.
- rswail 5y agoWhatever language is used, there is a choice of either positional or named arguments. Consistently using named arguments for a CLI to an API seems to be a good idea. Nothing to do with whether the API is written in Java. All of the AWS CLI support input in JSON or YAML as well and will generate the skeleton of the call for you as well.