AWS is run like a gigantic social experiment in "how half-assed and crusty can we make it and still have people pay?"
The reason we put up with them is because A. they're the new IBM, nobody gets fired for choosing AWS, B. you can reliably reach a human who will at least give you a straight answer when you start to suspect that the AI-powered auto-scaling is actually marketing fluff sprayed over a double/halve cron job that runs at the top of the hour.
>B. you can reliably reach a human who will at least give you a straight answer when you start to suspect that the AI-powered auto-scaling is actually marketing fluff sprayed over a double/halve cron job that runs at the top of the hour.
You say this as if it's an afterthought as opposed to an incredibly important and massive advantage AWS has over GCP.
^ My impression as well, after spending nearly $200K of my clients' money on AWS. I use GCP for my own work (+ a bunch of on-prem hardware) FWIW, but "the new IBM" phenomenon and "half assedness" is very real and palpable in the case of AWS.
Off-topic, but this might be a good opportunity to address this:
Do people find "?" as being aggressive? I think questions generally, tend to be aggressive (which is why deflecting back at your opponent is common in online arguments), and I'm having a hard time seeing how a question mark does more than just attempt to annoy the other person.
I'm curious what others think, I may be too sensitive.
Yep, that's how I intended it, effectively the same as "What?" with the implied offense level being no larger or smaller than the offense inherent in expressing surprise at someone else's opinion. That level is not zero, but it falls well within the bounds of civil discourse, especially given the lack of elaboration in the original position and the fact that I invested seventeen times its length on explaining my own -- only to not receive a followup from the original poster.
Yeah, next time I'll just type out the question. However, given that it's starting to look like OP ghosted the conversation, I'm increasingly comfortable with the originally-unintended rude undertones of "?"
Well it usually has been when I've personally used it.
There is the disdain of not explaining exactly what you are questioning with the implicit assumption you are questioning everything said. It's pretty much a stand-in for "WTF are you on about? I don't even know how to ask a sensible question about what you said." when I've used it.
In this case though? It's a single statement so maybe a bit abrupt but I read it as a request for clarification. A fairly strong statement was made (essentially "don't use this company") with no backup or explanation. So an equal lack of effort was made proportionally in response.
This is great for AWS compared to GCP, but what about Azure? If anyone was "the new IBM" I would have expected it to be Microsoft (but I agree, it's not).
Only if you forget to factor potential support problems into your economic analysis. What would your systems being down for a week because Google capriciously shut you down cost you?
True, but due to the large extent of the services provided/required, it's very hard to know the unexpected costs, even if one has experience.
For example, one will hardly think of the cost of the disk speed (IOPS, in AWS), before moving to AWS. Then, they will suddenly have to deal with it (note that IOPS will be mostly opportunity costs, in case one doesn't choose provisioned IOPS of larger capacity).
The cheapest provider in existence runs on renewables (Hetzner Online). There isn't too much of a difference, especially for EU datacenters as they have a high excess of renewables and the energy market works in a way where you pay for renewables but just as everyone else you'll be using the base capacity generating dirty sources.
AWS is run like a gigantic social experiment in "how half-assed and crusty can we make it and still have people pay?"
The reason we put up with them is because A. they're the new IBM, nobody gets fired for choosing AWS, B. you can reliably reach a human who will at least give you a straight answer when you start to suspect that the AI-powered auto-scaling is actually marketing fluff sprayed over a double/halve cron job that runs at the top of the hour.