3 ms·

It frustrates me how they always go for the biggest common denominator there, the lowest level shared by everyone, but what's hardly used by professional users:

It frustrates me how they always go for the biggest common denominator there, the lowest level shared by everyone, but what's hardly used by professional users: don't let me download a jar file, please give me Maven coordinates. Don't tell me how to click in the console to get an EC2 instance, please give me an example Terraform snippet. Don't just show me how AWS CLI returns a blob of JSON when I assume role, please tell me how to use aws-mfa properly. I understand and respect their hands off approach to these more opinionated tools. But ergo, I tend to skip over the Amazon properties when finding what I need in the search results! PS: Localstack is awesome! Also in combination with Testcontainers.

whummer 5y ago
+100 Another example to add to your list - the new AWS CLI v2: > don't force me to download a 30MB binary with embedded Python interpreter baked in, please just give us a pip package instead! ;)
- Sanguinaire 5y ago
  Or better yet, rewrite it in Go to avoid both the fat blob and python dependency management at the same time!
  - whummer 5y ago
    Touché!
  - chrsig 5y ago
    i mean, the go binary would still probably be a bit large, but having a statically linked binary to copy around would be welcome.
  - onetom 5y ago
    Or put the API definitions into some database (sqlite, datascript + nodejs or babashka or nbb), then you can decide what http library or mocked http solution would you like to use, eg https://github.com/oliyh/martian https://github.com/oliyh/martian Most of the code is just a thin veneer over that information...
- ed_elliott_asc 5y ago
  I’ve been on both sides of this and some consumers are fine but some have no idea how to consume or initial setup is so broken, this is much easier
  - whummer 5y ago
    Right, no doubt that some customers required fully packaged solutions. I guess it's generally hard to find the right balance, if you're catering to customers of different level of technical expertise/maturity. (Btw, the previous comment was in reference to: https://github.com/aws/aws-cli/issues/4947 https://github.com/aws/aws-cli/issues/4947)
- brentcetinich 5y ago
  aws cli v2 is such a sad story long live awscli1!

whummer 5y ago

+100 Another example to add to your list - the new AWS CLI v2: > don't force me to download a 30MB binary with embedded Python interpreter baked in, please just give us a pip package instead! ;)

Sanguinaire 5y ago
Or better yet, rewrite it in Go to avoid both the fat blob and python dependency management at the same time!
- whummer 5y ago
  Touché!
- chrsig 5y ago
  i mean, the go binary would still probably be a bit large, but having a statically linked binary to copy around would be welcome.
- onetom 5y ago
  Or put the API definitions into some database (sqlite, datascript + nodejs or babashka or nbb), then you can decide what http library or mocked http solution would you like to use, eg https://github.com/oliyh/martian https://github.com/oliyh/martian Most of the code is just a thin veneer over that information...
ed_elliott_asc 5y ago
I’ve been on both sides of this and some consumers are fine but some have no idea how to consume or initial setup is so broken, this is much easier
- whummer 5y ago
  Right, no doubt that some customers required fully packaged solutions. I guess it's generally hard to find the right balance, if you're catering to customers of different level of technical expertise/maturity. (Btw, the previous comment was in reference to: https://github.com/aws/aws-cli/issues/4947 https://github.com/aws/aws-cli/issues/4947)
brentcetinich 5y ago
aws cli v2 is such a sad story long live awscli1!