3 ms·

I will offer a very tepid "I've seen worse" for AWS's UI considering all the things it has to support. That said, the redesign made it worse (those scroll wind

I will offer a very tepid "I've seen worse" for AWS's UI considering all the things it has to support. That said, the redesign made it worse (those scroll windows that don't fill up the pane... MY GOD HOW DO YOU NOT FIX THAT), there is no sense of continual improvement and addition of useful new features and views, performance is pretty bad. All I ever hear "you're not supposed to use the UI, you're supposed to use the API". Don't get me started on the API. This quiz is missing these three key points: - has culled 1,000$ annual savings in a AWS cost saving review? - has culled 10,000$ annual savings in an AWS cost saving review? - has culled 100,000$ ? - has culled 1,000,000$? I ... almost .. got to 1,000,000 once. - trapped AWS support in an outright lie? - gotten AWS support to tell you results of hidden internal metrics to debug something?

jackson1442 4y ago
> Don't get me started on the API. At least it's not the GCP API. Had to use that for some compliance automation once and still have nightmares about it.
- kccqzy 4y ago
  Why not use the CLI though? The aws and gcloud CLI tools seem fine when I occasionally use them.
  - jackson1442 4y ago
    Ah, read API as CLI (with AWS they're essentially the same). The biggest problem with GCP's api/cli/sdk/console is they're not the same. There are things you can only do in the console, or have different grammars across CLI/SDK, or have different permission schemes across them. Add to that the intermixing of "IT Admin" and "Cloud Admin" roles due to all of your Google Groups also being IAM groups, and IAM being somehow tied into your G Suite admin area, it's just a confusing mess. With AWS, the CLI is the API is the SDK. So if you can use one, you can use all of them very easily.
    - scarface74 4y ago
      It’s all based on the same specification and all of the SDKs and the CLI are autogenerated.
  - ahtihn 4y ago
    CLIs are not great at showing you the operations that are available to you. Exploring what's possible is much easier with a GUI in my experience.
somethingAlex 4y ago
Yeah I'm always surprised by the downright hate. I use the console for 95% of things and it's alright. My gripe is that the thing just gives off this BLOATED impression. Safari routinely reloads it because it was "using significant energy." Every time I load a page I just wait until it renders, goes blank, re-renders, goes blank, places everything that was on the left over to the right, and then finally things settle down and I click a button. That all takes about 1.5s though, so not awful.

jackson1442 4y ago

> Don't get me started on the API. At least it's not the GCP API. Had to use that for some compliance automation once and still have nightmares about it.

kccqzy 4y ago
Why not use the CLI though? The aws and gcloud CLI tools seem fine when I occasionally use them.
- jackson1442 4y ago
  Ah, read API as CLI (with AWS they're essentially the same). The biggest problem with GCP's api/cli/sdk/console is they're not the same. There are things you can only do in the console, or have different grammars across CLI/SDK, or have different permission schemes across them. Add to that the intermixing of "IT Admin" and "Cloud Admin" roles due to all of your Google Groups also being IAM groups, and IAM being somehow tied into your G Suite admin area, it's just a confusing mess. With AWS, the CLI is the API is the SDK. So if you can use one, you can use all of them very easily.
  - scarface74 4y ago
    It’s all based on the same specification and all of the SDKs and the CLI are autogenerated.
- ahtihn 4y ago
  CLIs are not great at showing you the operations that are available to you. Exploring what's possible is much easier with a GUI in my experience.

somethingAlex 4y ago

Yeah I'm always surprised by the downright hate. I use the console for 95% of things and it's alright. My gripe is that the thing just gives off this BLOATED impression. Safari routinely reloads it because it was "using significant energy." Every time I load a page I just wait until it renders, goes blank, re-renders, goes blank, places everything that was on the left over to the right, and then finally things settle down and I click a button. That all takes about 1.5s though, so not awful.