<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>lukev</author><text>Here are some better names for S3 that aren&amp;#x27;t misleading:&lt;p&gt;- Binary Storage&lt;p&gt;- Blob Storge&lt;p&gt;- File Storage&lt;p&gt;- Reliable Storage&lt;p&gt;FTP is a specific protocol. Hard drives (as a sibling comment mentions) are a specific technology. Our discipline is confusing enough that names should be precise, not analogical.</text><parent_chain><item><author>sadok</author><text>You are missing the whole point. As a designer that dabbles a bit in code and servers, I literally have NO idea what most of the words you just used mean.&lt;p&gt;I know that S3 has nothing to do with FTP, but it&amp;#x27;s a nice analogy that I can relate to. Get off your high horse.</text></item><item><author>lukev</author><text>Sure, a lot of AWS services could have been named better. But a lot of these are terrible, downright misleading names.&lt;p&gt;Some examples:&lt;p&gt;S3 as &amp;quot;Amazon Unlimited FTP Server&amp;quot;: S3 has nothing to do with the FTP protocol.&lt;p&gt;VPC as &amp;quot;Amazon Virtual Collocated Rack&amp;quot;: VPCs don&amp;#x27;t have anything to do with either collocation (they can span AZs), much less physical racks.&lt;p&gt;Lambda as &amp;quot;AWS App Scripts&amp;quot;: &lt;i&gt;really&lt;/i&gt; disagree with this one. Their intent is to be microservices or event handling functions, not scripts. &amp;quot;Scripts&amp;quot; isn&amp;#x27;t really descriptive but usually implies a manually invoked automation that modifies some kind of stateful resource (such as files). Lambda is basically the exact opposite.&lt;p&gt;There are lots more that are problematic or overly simplified as well.&lt;p&gt;I don&amp;#x27;t say this to crap on the effort, just... be careful if you&amp;#x27;re relying on this for your understanding of what AWS does.</text></item></parent_chain></comment><story><title>Amazon Web Services in Plain English</title><url>https://www.expeditedssl.com/aws-in-plain-english</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>thekelvinliu</author><text>the original comment offers some constructive criticism because the article does have the potential to misinform novice users about what certain services do and the technologies they use. yours is more of a directed personal attack; keep in mind that this is hn. good on you for knowing a priori s3 is not ftp. but i wouldn&amp;#x27;t expect someone new to development to necessarily know this. as a result, they could have an even harder time figuring out how to do things if, for example, they search for advice on how to connect to the s3 ftp server.</text><parent_chain><item><author>sadok</author><text>You are missing the whole point. As a designer that dabbles a bit in code and servers, I literally have NO idea what most of the words you just used mean.&lt;p&gt;I know that S3 has nothing to do with FTP, but it&amp;#x27;s a nice analogy that I can relate to. Get off your high horse.</text></item><item><author>lukev</author><text>Sure, a lot of AWS services could have been named better. But a lot of these are terrible, downright misleading names.&lt;p&gt;Some examples:&lt;p&gt;S3 as &amp;quot;Amazon Unlimited FTP Server&amp;quot;: S3 has nothing to do with the FTP protocol.&lt;p&gt;VPC as &amp;quot;Amazon Virtual Collocated Rack&amp;quot;: VPCs don&amp;#x27;t have anything to do with either collocation (they can span AZs), much less physical racks.&lt;p&gt;Lambda as &amp;quot;AWS App Scripts&amp;quot;: &lt;i&gt;really&lt;/i&gt; disagree with this one. Their intent is to be microservices or event handling functions, not scripts. &amp;quot;Scripts&amp;quot; isn&amp;#x27;t really descriptive but usually implies a manually invoked automation that modifies some kind of stateful resource (such as files). Lambda is basically the exact opposite.&lt;p&gt;There are lots more that are problematic or overly simplified as well.&lt;p&gt;I don&amp;#x27;t say this to crap on the effort, just... be careful if you&amp;#x27;re relying on this for your understanding of what AWS does.</text></item></parent_chain></comment><story><title>Amazon Web Services in Plain English</title><url>https://www.expeditedssl.com/aws-in-plain-english</url></story>