4 ms·

So, if I understand this right, you're getting really really worked up at a slightly tongue-in-cheek post that tries to explain AWS in a way that's relateable t

So, if I understand this right, you're getting really really worked up at a slightly tongue-in-cheek post that tries to explain AWS in a way that's relateable to a lot of programmers. And you're upset because the words used in this post, which is about explaining Amazon's services to people who are familiar with similar services, wouldn't be a wise choice for Amazon to actually use, since it's too familiar with their competition? That seems silly, and kind of missing the entire point of this submission. I haven't used any of Amazon's services, so having something to translate back to things I can understand was really helpful, and I feel like I have a much better idea of what Amazon offers.

ins0 11y ago
Exactly what i was thinking about as i submited this. Don't read this article as a "They should rename the Services to..." and more like "This name would explain the Service in a simpler form". Thanks for reading my mind btw :)
- stephenr 11y ago
  Simpler or easier to recognise by some, but wrong is hardly better.
stephenr 11y ago
I wouldn't call this worked up or upset. The post claims to have "better hames" for the AWS services. Many of those names are much worse. Take the suggested "Amazon Beginning Cut Pro" which was their suggestion for "Elastic Transcoder". "Beginning Cut Pro" is clearly a reference to Apple's NLE, Final Cut Pro. I would suggest that there are literally zero people on the planet, who would use Amazon's video transcoding service (I imagine it's essentially a distributed ffmpeg queue.) to process video files before importing them into FCP. This isn't "tongue in cheek", this is "stupid and confusing as an attempt at a laugh". I mean, what if I suggested that a hosted Memcached service be called AppStart because it uses memory and Apps use memory. > having something to translate back to things I can understand was really helpful My issue is that several of the services covered, already have a MORE MEANINGFUL name. So if I had no idea what "Elastic Transcoder" did, but it was instead called "Amazon Beginning Cut Pro", I would then assume it's somehow a tool meant to work with FCP, and disregard it (I don't need a NLE, at most maybe I need something akin to ffmpeg, so I can transcode/scale video files between formats automatically and efficiently. If it's comedy, call it comedy, and make it actually funny. If it's meant to be a useful guide, make it fucking accurate, or it's worse than what AWS is doing already.
- numbnuts 11y ago
  I wouldn't want to be around you when you're actually worked up. I found it both funny and useful. But I can see where you're coming from. If I wanted something fucking accurate that goes into greater fucking detail than 1-2 mostly tongue-in-cheek sentences I'd go to the fucking source.
  - stephenr 11y ago
    The fucking source is confusing, remember? This is frankly just as confusing for different reasons. It isn't funny enough to be considered comedy so I honestly don't understand the point.

ins0 11y ago

Exactly what i was thinking about as i submited this. Don't read this article as a "They should rename the Services to..." and more like "This name would explain the Service in a simpler form". Thanks for reading my mind btw :)

stephenr 11y ago
Simpler or easier to recognise by some, but wrong is hardly better.

stephenr 11y ago

I wouldn't call this worked up or upset. The post claims to have "better hames" for the AWS services. Many of those names are much worse. Take the suggested "Amazon Beginning Cut Pro" which was their suggestion for "Elastic Transcoder". "Beginning Cut Pro" is clearly a reference to Apple's NLE, Final Cut Pro. I would suggest that there are literally zero people on the planet, who would use Amazon's video transcoding service (I imagine it's essentially a distributed ffmpeg queue.) to process video files before importing them into FCP. This isn't "tongue in cheek", this is "stupid and confusing as an attempt at a laugh". I mean, what if I suggested that a hosted Memcached service be called AppStart because it uses memory and Apps use memory. > having something to translate back to things I can understand was really helpful My issue is that several of the services covered, already have a MORE MEANINGFUL name. So if I had no idea what "Elastic Transcoder" did, but it was instead called "Amazon Beginning Cut Pro", I would then assume it's somehow a tool meant to work with FCP, and disregard it (I don't need a NLE, at most maybe I need something akin to ffmpeg, so I can transcode/scale video files between formats automatically and efficiently. If it's comedy, call it comedy, and make it actually funny. If it's meant to be a useful guide, make it fucking accurate, or it's worse than what AWS is doing already.

numbnuts 11y ago
I wouldn't want to be around you when you're actually worked up. I found it both funny and useful. But I can see where you're coming from. If I wanted something fucking accurate that goes into greater fucking detail than 1-2 mostly tongue-in-cheek sentences I'd go to the fucking source.
- stephenr 11y ago
  The fucking source is confusing, remember? This is frankly just as confusing for different reasons. It isn't funny enough to be considered comedy so I honestly don't understand the point.