<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>dzonga</author><text>Jonathan Blow&amp;#x27;s Preventing the Collapse of Civilization [0] is an excellent talk, on how too much abstractions destroy knowledge.&lt;p&gt;This is a problem with the software industry today. we have forgotten how to do the simple stuff, that works and is robust.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=ZSRHeXYDLko&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=ZSRHeXYDLko&lt;/a&gt;</text><parent_chain><item><author>movedx</author><text>F- me. I love this. This is a really important message.&lt;p&gt;It&amp;#x27;s like Jonathon Blow asks: why does Photoshop take longer to load today than it did in the 90s despite the (insane) advances in hardware?&lt;p&gt;I believe it&amp;#x27;s due to a bunch of things, but over complicating the entire process is one of the big issues. If people (developers&amp;#x2F;engineers) would only sit back and realise just how much computing power they have available to them, and then realised that if they kept things simple and efficient, they could build blazing fast solutions over night.&lt;p&gt;I cringe thinking about the wasted opportunities out there.</text></item><item><author>SatvikBeri</author><text>Several years ago, I was chatting with another engineer from a close competitor. He told me about how they&amp;#x27;d set up a system to run hundreds of data processing jobs a day over a dozen machines, using docker, load balancing, a bunch of AWS stuff. I knew these jobs very well, they were basically identical for any company in the space.&lt;p&gt;He then mentioned that he&amp;#x27;d noticed that somehow my employer had been processing thousands of jobs, much faster than his, and asked how many machines we were using.&lt;p&gt;I didn&amp;#x27;t have the heart to tell him we were running everything manually on my two-year-old macbook air.</text></item><item><author>systemvoltage</author><text>Along with this, vertical scaling is severely underrated. You can do a lot and possibly &lt;i&gt;everything ever&lt;/i&gt; for your company with vertical scaling. It would apply to 99% of the companies or even more.&lt;p&gt;Edit:
Since people are confused, here is how StackOverflow handles of all of its web operations. If SO can run with this, so can your 0.33 req&amp;#x2F;minute app which is mostly doomed for failure. I am only half joking.&lt;p&gt;StackOverflow architecture, current load (it will surprise you): &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackexchange.com&amp;#x2F;performance&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackexchange.com&amp;#x2F;performance&lt;/a&gt;&lt;p&gt;Everytime you go to SO, it hits one of these 9 web servers and all data on SO sits on those 2 massive SQL servers. That&amp;#x27;s pretty amazing.&lt;p&gt;I want to be clear though, Horizontal scaling has a place in companies that has a team of corporate lawyers. Big. And in many many other scenarios for ETL and backend microservices.</text></item></parent_chain></comment><story><title>We Don’t Use Docker</title><url>https://launchyourapp.meezeeworkouts.com/2021/03/why-we-dont-use-docker-we-dont-need-it.html?m=1</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>mason55</author><text>I think there are two things that cause this.&lt;p&gt;One is that there’s a minimum performance that people will tolerate. Beyond that you get quickly diminishing user satisfaction returns when trying to optimize.  The difference between 30 seconds and 10 seconds in app startup time isn’t going to make anyone choose or not choose Photoshop. People who use PS a lot probably keep it open all day and everyone else doesn’t care enough about the 20 seconds.&lt;p&gt;The second problem is that complexity scales super-linearly with respect to feature grown because each feature interacts with every other feature.  This means that the difficulty of optimizing startup times gets harder as the application grows in complexity.  No single engineer or team of engineers could fix the problem at this point, it would have to be a mandate from up high, which would be a silly mandate since the returns would likely be very small.</text><parent_chain><item><author>movedx</author><text>F- me. I love this. This is a really important message.&lt;p&gt;It&amp;#x27;s like Jonathon Blow asks: why does Photoshop take longer to load today than it did in the 90s despite the (insane) advances in hardware?&lt;p&gt;I believe it&amp;#x27;s due to a bunch of things, but over complicating the entire process is one of the big issues. If people (developers&amp;#x2F;engineers) would only sit back and realise just how much computing power they have available to them, and then realised that if they kept things simple and efficient, they could build blazing fast solutions over night.&lt;p&gt;I cringe thinking about the wasted opportunities out there.</text></item><item><author>SatvikBeri</author><text>Several years ago, I was chatting with another engineer from a close competitor. He told me about how they&amp;#x27;d set up a system to run hundreds of data processing jobs a day over a dozen machines, using docker, load balancing, a bunch of AWS stuff. I knew these jobs very well, they were basically identical for any company in the space.&lt;p&gt;He then mentioned that he&amp;#x27;d noticed that somehow my employer had been processing thousands of jobs, much faster than his, and asked how many machines we were using.&lt;p&gt;I didn&amp;#x27;t have the heart to tell him we were running everything manually on my two-year-old macbook air.</text></item><item><author>systemvoltage</author><text>Along with this, vertical scaling is severely underrated. You can do a lot and possibly &lt;i&gt;everything ever&lt;/i&gt; for your company with vertical scaling. It would apply to 99% of the companies or even more.&lt;p&gt;Edit:
Since people are confused, here is how StackOverflow handles of all of its web operations. If SO can run with this, so can your 0.33 req&amp;#x2F;minute app which is mostly doomed for failure. I am only half joking.&lt;p&gt;StackOverflow architecture, current load (it will surprise you): &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackexchange.com&amp;#x2F;performance&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackexchange.com&amp;#x2F;performance&lt;/a&gt;&lt;p&gt;Everytime you go to SO, it hits one of these 9 web servers and all data on SO sits on those 2 massive SQL servers. That&amp;#x27;s pretty amazing.&lt;p&gt;I want to be clear though, Horizontal scaling has a place in companies that has a team of corporate lawyers. Big. And in many many other scenarios for ETL and backend microservices.</text></item></parent_chain></comment><story><title>We Don’t Use Docker</title><url>https://launchyourapp.meezeeworkouts.com/2021/03/why-we-dont-use-docker-we-dont-need-it.html?m=1</url></story>