Today’s JavaScript, from an outsider’s perspective (2020)
The author encounters four problems trying to approach a programming task:<p>1) A problem common to every programming language (feature introduction&#x2F;deprecation compatibility conflicts w.r.t. import&#x2F;require)<p>2) A security issue around browser filesystem access (not-JS related at all: HTTP content-type sniffing)<p>3) A usability issue with  the VSCode IDE (not JS related)<p>4) A bug in a single JS module<p>Concludes this is all the fault of &quot;modern Javascript&quot;, gives up.<p>&gt; <i>What hope do actual novices have?</i><p>Programming is a profession requiring learning from experience - if a novice doesn&#x27;t have the patience to overcome very small speedbumps like this <i>on a daily basis</i> while learning a new domain, this might not be a good path for them.<p>Don&#x27;t get me wrong, there&#x27;s A LOT about the modern JS ecosystem that could be improved from a UX perspective, but... it&#x27;s not these things. I don&#x27;t think any of the 4 bullets above are avoidable: (1) is a painful but necessary migration incompatibility is an unfortunate reality, the only alternative of which is to stagnate and never introduce&#x2F;deprecate breaking features ever. (4) is human error - it happens. The others aren&#x27;t JS-related at all.