<story><title>Programs are dead, and JavaScript has killed them</title><url>https://pouria.dev/programs-are-dead/</url></story><parent_chain><item><author>mouzogu</author><text>&amp;gt; During the past 5–6 years of my JavaScript experience, every time I wanted to go back to any of my projects—from tiny to big, server-side or front-end—there was always a challenge, a problem to tackle or an obstacle to overcome before I can update or sometimes even just run my program.&lt;p&gt;why i moved mostly from writing node cmd tools to using bash. don&amp;#x27;t need to go on a bunch of side missions every time i run npm install&lt;p&gt;not enough pragmatism in the JS &lt;i&gt;community&lt;/i&gt; (people). more about hot new thing as opposed to boring long term stability. maybe because of web&amp;#x2F;chrome as a constantly moving platform, and Apple&amp;#x2F;Jobs app-ification of everything, relative young age of JS community.</text></item></parent_chain><comment><author>cxr</author><text>It&amp;#x27;s funny.  The issue described (inability to replicate the conditions to build and&amp;#x2F;or run the original program using NPM) is something that gets brought up a lot, but people will appear who are downright adamant that it&amp;#x27;s not a problem.  Not just that it&amp;#x27;s not prevalent enough to be concerned about, but that they&amp;#x27;ve literally never seen it happen ever.  We&amp;#x27;re living in completely separate worlds.&lt;p&gt;And let&amp;#x27;s be clear: this is an *NPMJS* problem, not a *JS* problem.  For folks who have read and written lots of JS before and during NPM&amp;#x27;s reign over programmers&amp;#x27; attention and will continue to do so afterward (when NPM as the dominant culture evaporates) and have kept NPM- and NodeJS-inspired &amp;quot;best practices&amp;quot; at arms length precisely for these reasons and more, it&amp;#x27;s irksome to see people full-on equate JS with what-the-NPMers-are-doing.</text></comment>
<story><title>Programs are dead, and JavaScript has killed them</title><url>https://pouria.dev/programs-are-dead/</url></story><parent_chain><item><author>mouzogu</author><text>&amp;gt; During the past 5–6 years of my JavaScript experience, every time I wanted to go back to any of my projects—from tiny to big, server-side or front-end—there was always a challenge, a problem to tackle or an obstacle to overcome before I can update or sometimes even just run my program.&lt;p&gt;why i moved mostly from writing node cmd tools to using bash. don&amp;#x27;t need to go on a bunch of side missions every time i run npm install&lt;p&gt;not enough pragmatism in the JS &lt;i&gt;community&lt;/i&gt; (people). more about hot new thing as opposed to boring long term stability. maybe because of web&amp;#x2F;chrome as a constantly moving platform, and Apple&amp;#x2F;Jobs app-ification of everything, relative young age of JS community.</text></item></parent_chain><comment><author>Gibbon1</author><text>A month ago I found a bug in command line utility I wrote in C# and hadn&amp;#x27;t touched in 8 years. I checked out the project and opened it in Visual Studio. And it compiled. I fixed the bug and it just worked. End to end it took half an hour. I feel like there is an advantage to libraries and tools managed by adults with long term skin in the game.</text></comment>