De-facto closed source: the case for understandable software
The more I read about the js ecosystem, the more it seems the inmates are running the asylum<p>It&#x27;s a long time since js needed a good stdlib.<p>Everybody was using this package but apparently no one but an adversarial player stepped up to actually maintain it.<p>(And don&#x27;t get me started on &quot;let&#x27;s always get the latest version of the package&quot;)<p>&gt; You want to download thousands of lines of useful, but random, code from the internet, for free, run it in a production web server, or worse, your user’s machine, trust it with your paying users’ data and reap that sweet dough. We all do. But then you can’t be bothered to check the license, understand the software you are running and still want to blame the people who make your business a possibility when mistakes happen, while giving them nothing for it? This is both incompetence and entitlement.<p>Not surprising. Not surprising in the least. &quot;Oh wow somebody 0wned the package I needed&quot;. Maybe because js projects have <i>an order of magnitude more dependencies</i> than a Python&#x2F;Java&#x2F;Go, etc project. Maybe because in the extreme opposite of NIH, people feel the need to import a module for every small thing they want to do? &quot;Stack overflow programming&quot;, &quot;how do I add 2 numbers using React, is there a module for that!?!?!&quot;