<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dasil003</author><text>I&amp;#x27;m not sure any sizable group is banging their head against a wall.  Yes, AWS is complex. Yes, AWS has cost foot guns.  These are natural outcomes of removing friction from scaling.&lt;p&gt;Sure we could start with something simpler, but as you may have noticed, even the more basic hosting providers like DigitalOcean and Linode have been adding S3-compatible object storage because of its proven utility.&lt;p&gt;In terms of making something meaningfully simpler, I think Heroku was the high water mark. But even though it was a great developer experience, the price&amp;#x2F;performance barriers were a lot more intractable than dealing with AWS.</text><parent_chain><item><author>asim</author><text>The AWS horror stories never cease to amaze me. It&amp;#x27;s like we&amp;#x27;re banging our heads against the wall expecting a different outcome each time. What&amp;#x27;s more frustrating, the AWS zealots are quite happy to tell you how you&amp;#x27;re doing it wrong. It&amp;#x27;s the users fault for misusing the service. The reality is, AWS was built for a specific purpose and demographic of user. It&amp;#x27;s now complexity and scale makes it unusable for newer devs. I&amp;#x27;d argue, we need a completely new experience for the next generation.</text></item></parent_chain></comment><story><title>AWS S3: Sometimes you should press the $100k button</title><url>https://www.cyclic.sh/posts/aws-s3-why-sometimes-you-should-press-the-100k-dollar-button</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rmbyrro</author><text>What do you see missing or not well explained in AWS documentation that newer devs wouldn&amp;#x27;t understand?&lt;p&gt;I started using S3 early in my career and didn&amp;#x27;t see this problem. I always thought in data retention during design phase.&lt;p&gt;My opinion is that lazy, careless or under time pressure developers will not, and then will get bitten. But it would happen to any tool. Maybe a different problem, but they&amp;#x27;ll always get bitten hard   ...</text><parent_chain><item><author>asim</author><text>The AWS horror stories never cease to amaze me. It&amp;#x27;s like we&amp;#x27;re banging our heads against the wall expecting a different outcome each time. What&amp;#x27;s more frustrating, the AWS zealots are quite happy to tell you how you&amp;#x27;re doing it wrong. It&amp;#x27;s the users fault for misusing the service. The reality is, AWS was built for a specific purpose and demographic of user. It&amp;#x27;s now complexity and scale makes it unusable for newer devs. I&amp;#x27;d argue, we need a completely new experience for the next generation.</text></item></parent_chain></comment><story><title>AWS S3: Sometimes you should press the $100k button</title><url>https://www.cyclic.sh/posts/aws-s3-why-sometimes-you-should-press-the-100k-dollar-button</url></story>