If AWS was as shaky as Amazon.com goods, nobody would use it.
If AWS was as shaky as Amazon.com goods, nobody would use it.
Example: You might've heard a phrase like "I was literally blown away by the response I got" (probably from a vlogger). Nobody in English would say, "I was figuratively blown away by the response I got", because it's obvious the person is speaking figuratively.
Here, literally is meant to emphasize just how effective AWS is acting analogously to the Treasury's money printing presses.
So, I'm with GP: the word "literally" doesn't fit the context and ought to be replaced.
I'm all for treating language as the living thing it is. However, "literally" is a very useful word and there's noting else quite like it.
If "literally" can mean both literally and the exact opposite of literally, it becomes devoid of meaning.
[0]: https://www.oed.com/view/Entry/109061 definition 1c
Steven Pinker wrote about this in detail in The Language Instinct.
https://www.grammarphobia.com/blog/2007/01/i-could-care-less...
When someone says "I literally could care less", everyone listening knows what they mean. There is no confusion and no need to worry about whether they are literally correct.
This is just part of the fun and wonder of the English language.
When I hear someone say "I could care less" when they mean "I couldn't care less" then I tend to understand that they value their words, language, and meaning less than I do mine. They're unintentionally signaling to me that what they're saying isn't necessarily what they mean, and so I factor that into my understanding of, belief in, and reliance upon, whatever they may say.
Most people don't think about linguistics regularly. Their ignorance on a topic doesn't mean they would or would not be passionate about it, had they known more.
But people who say "I could care less" are usually not mistaken. They know full well what they mean, and that the phrase seems to say the opposite of its literal meaning.
It's a great example of irony and sarcasm, both of which have a rich history in English, and probably in most languages.
Pinker has a fine discussion of the phrase in the book I mentioned. I can't do it justice here, but consider how the phrase is spoken. I will use italics to indicate emphasis:
I could care less.
Try saying that out loud a few times with emphasis on the italicized words. You may start to hear the ironic and sarcastic intent.
English would be a much poorer language if we could only use words and phrases in their most literal meaning.
Also consider the context. "I could care less" is used in casual speech, where it's perfectly OK to play with the language and have fun with it.
That is quite different from, say, a manual on how to operate a piece of machinery, or any other kind of technical documentation. There of course you want to be as clear, explicit, and unambiguous as possible.
But I wouldn't judge someone's ability to write a clear technical manual based on their enjoyment of irony in more casual speech or writing.
They know what they mean, but they're not expressing some deep irony or sarcasm. They're just parroting back something they've heard someone else say-- incorrectly.
But yeah, sometimes we just make a mistake.
Haven't we all uttered a malapropism at one time or another?
I love watching a flamingo dance!
Consider the related “it’s possible for me to care less” suggesting a preference exists, but it’s negligible. That’s generally how people mean “I could care less”. Which oddly enough means the literal difference between “I (could/couldn’t) care less.” is practically meaningless.
When someone says "it's literally a printing press" about something that is obviously not a printing press, you know that they are using literally as it has been used for hundreds of years[0]: for strong emphasis.
[0]: https://www.oed.com/view/Entry/109061 definition 1c.
I used to argue the other way too, then one day on a whim I looked it up. I was surprised.
"Informal" tends to mean "wrong", "bastardised", or "misappropriated". So I think we're all actually on the same page.
For what its worth, Amazon Retail has been (or could be, depending on quarter) profitable on its own. It's certainly not a shaky business model, shaky margins maybe. Similarly, Uber is a sound business model (taxis exist for a while), just an unsound price point.
Amazon is operating weirdly (random pricing now) even though it's true the financial side is probably normal.
- EC2, including scaling groups (but crucially do not attempt to use them for auto-scaling)
- S3
- Route53
- RDS
- Redshift
- Maybe a few others I've forgotten or haven't used
They all have their flaws, but if you stay on the beaten path, they basically work most of the time.
Then there is the other AWS. It consists of all the other high level services you can pick from that enormous drop-down. I haven't tried many, but from my little experience and loaaaads of anecdotes from other people, _that_ AWS is largely unreliable rubbish.
That is to say, stick to the extremely common low-level or otherwise foundational stuff unless you love pain and disappointment.
But the thrust of your point remains: when you get into the nonsense factory, when you're trying to bolt together the higher level integrated services, it becomes an exercise in self-inflicted stochastic violence.
The true AWS advantage is that the boss can't get fired for choosing it so the individual contributors already have spending authority inside its walls. Unfortunately, that's a trump card.
The main reason you hear about so much Azure growth is because they give free credits to their software assurance customers. For everyone else, not work paying for it.