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?
At least it's not the GCP API. Had to use that for some compliance automation once and still have nightmares about it.
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.
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.
Who is the "they" in that sentence? Each AWS product team writes their own console UI, as far as I know, and they're free to do pagination however it makes sense for them.
(Of course my question doesn't really matter because they're all pretty middling.)
And even if they can't change the API, the front-end could request the next page from the API until they have a full page to display.
It's certainly not just you. I've complained about it at work parties at AWS, and so did my colleagues.
I was on a front end team working on the AWS Console for a fairly well known service.
Good to know it’s not just me (but seriously, the way they’ve implemented search in paginated results is the most actively hostile UX decision I’ve ever encountered. It’s so bad it almost makes me feel better about the half-baked hacky stuff I’ve done over the years.)