It&#x27;s a matter of scale.<p>Of course you can put anything you want up online (and you should!).  But, if you have (or expect to have) millions of users, then one person sitting alone saying &quot;ME ME ME&quot; doesn&#x27;t cut it.<p>It stops being less <i>about fun</i> when your company loses $10,000 per minute of downtime and you suffer an outage because you are operating &quot;at-scale&quot; (256 GB RAM to 1 TB RAM, thousands of clustered servers, multi-datacenter replication, etc) but your software is only tested on the primary developer&#x27;s macbook air.<p>Rejecting the feedback of people with actual experience running large scale systems in favor of one person&#x27;s unexperienced narrow viewpoints is just bananas.  Large scale software <i>can&#x27;t</i> operate under single minded &quot;open source fascism&quot; anymore because our computing world is too complicated these days.<p>With millions of users you&#x27;ll have people using your software for critical systems needing things like uptime, reliability, timely security fixes, timely bug fixes, etc.  When you start getting 50 requests a day for changes, you will seem inept just telling everyone &quot;lol its my software i do whatever i want you should just go away and fork it you can&#x27;t tell me what to do.&quot;<p>It&#x27;s professionally irresponsible to run a project with millions of users without a scalable team of equal contributors.<p>The argument against companies running their systems on top of poorly maintained&#x2F;developed&#x2F;supported open source software (while still expecting free and immediate improvements&#x2F;fixes) is an entirely different article though.