I think the point is obvious, that AWS is far more customer-centric than GCP. Google's gotten better at this but at the time, it seemed to me that GCP was more an amalgam of individual projects developed separately while AWS approached it more from the user's perspective, and that showed in the toolsets available.
I am really trying not to sound like a GCP fanboy, however:
I have never heard anyone say that the AWS toolset was anything but "an amalgam of individual projects developed separately." It is obvious from their UI that the different tools are run by different teams that have very different opinions on how things should be done. Just look at the various iterations of deployment management. ECS vs Lambda vs EKS vs classic EC2. All the UIs have different design standards and assumptions. It has gotten better over the years, but the AWS org chart is still peaking through the UI.
GCP is not much better. At least they had the advantage of starting later in the market cycle. They were able to see what worked and what didn't work at AWS and build a bit cleaner.
In the end we are talking about B2B systems targeting power user engineers. The control surfaces need to be powerful first, and easy to use is a distant second or third consideration.
