<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[JavaScript Non Grata - Medium]]></title>
        <description><![CDATA[Just say no to this abomination - Medium]]></description>
        <link>https://medium.com/javascript-non-grata?source=rss----3fcce414cbc9---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>JavaScript Non Grata - Medium</title>
            <link>https://medium.com/javascript-non-grata?source=rss----3fcce414cbc9---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:48:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/javascript-non-grata" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Five Top Reasons to Use JavaScript]]></title>
            <link>https://medium.com/javascript-non-grata/the-five-top-reasons-to-use-javascript-bd0c0917cf49?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/bd0c0917cf49</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Sat, 28 May 2016 08:15:26 GMT</pubDate>
            <atom:updated>2018-08-08T13:39:53.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*azrSFrHs_UCAeuvIbAdDzg.png" /><figcaption>Happy Happy Joy Joy</figcaption></figure><h4>Reason #1:</h4><p><strong>JavaScript is very easy to learn. No setup is required; it’s built right into the web browser! Just start writing code and see the results immediately in your browser.</strong></p><p>I pity would-be software engineers who are too intimidated and lethargic to follow simple installation instructions for languages like Python, Ruby, Smalltalk, Go and Elixir. They lack the kind of initiative, curiosity and determination that is so necessary to becoming an IT professional.</p><p>Once you overcome <em>the huge, overbearing obstacle</em> of installing one of these languages, you’ll find that the syntax is wonderfully easy and inviting. They’ll make JavaScript look like the awkward stepchild that it is in the world of engineering.</p><h4>Reason #2:</h4><p><strong>JavaScript is used <em>everywhere</em>…web browser (Angular, React), server-side (Node), mobile, desktop, games, Internet of Things, robotics, virtual reality, etc.</strong></p><p>Hold your horses, not so fast! JavaScript dominates in web development because you have no choice — it’s the native language of the web browser. <em>Outside of the web</em>, JavaScript is up against many language competitors where it’s clearly disadvantaged. For example, in the mobile space, JavaScript has no hope of displacing Java (for Android) and Objective-C/Swift (for iOS).</p><p>On the desktop, JavaScript cannot compete with C++ and Java. In games, C++ and C# rule. Internet of Things? We’re looking at C, Python, Java, even Perl! Robotics means C/C++, Python, Java and Smalltalk. And so on.</p><p>Do you see a pattern? In every case, solid programming languages win the day. <a href="https://medium.com/javascript-non-grata/the-three-big-lies-about-javascript-e227cabe3beb">JavaScript is objectively a very flawed language</a>. That it has managed to be shoehorned into these different areas is a testament to the JavaScript community’s creativity, but we have to face the fact that, in practice, JavaScript is not gaining traction. <strong>JavaScript is used for web development.</strong> <a href="https://medium.com/@freemanlatif/after-react-elm-152bd6559cb1">Period</a>.</p><h4>Reason #3:</h4><p><strong>Node is super popular. Proof: there are over 30,000 NPM packages available!</strong></p><p>How many of these 30,000+ packages have significant usage? Probably relatively few. Let’s consider an Apple analogy. Apple claims that there are over 1.5 million iOS apps in the App Store. But it’s well-known that only a tiny percentage of them are popular. The rest lie fallow, never to see the light of day. In fact, I wrote an iOS app that has done absolutely squat in the App Store; I’m one of the sad statistics.</p><p>The fact that so many NPM packages exist shows the “gold rush” mentality that most contributors have. They hope to cash in on the JavaScript hype, or at least make a name for themselves in the open source community. Open source is another good example. Open source has countless thousands of contributions, most of which never see the light of day. So what do 30,000+ NPM packages signify?</p><p>Not much of anything. We still don’t know how many businesses use Node. Is it even in the thousands, for instance (show me the numbers)? Even that would pale in comparison to Java or Python usage.</p><h4>Reason #4:</h4><p><strong>There are lots of high-paying jobs for JavaScript developers. What a great way to start your IT career!</strong></p><p>It’s true, there are lots and lots of JavaScript job postings. And <strong>all </strong>of them are related to front-end web development or Node. You won’t find any postings for JavaScript programming in mobile, desktop, Internet of Things, games, robotics, virtual reality, etc. <em>If all you want to do is write web apps, then JavaScript may be your ticket.</em> But it’s hardly the path to a healthy career in IT, where there are so many other exciting developments going on, such as Artificial Intelligence, robotics, Big Data, Internet of Things, cloud computing, scientific modelling and simulation, Virtual Reality, etc., which use grown-up languages like Java, Python, C/C++, Go, Haskell and Julia.</p><h4>Reason #5:</h4><p><strong>JavaScript is an incredibly <em>expressive and powerful</em> language.</strong></p><p>Such an unbelievable overstatement! Is JavaScript any more expressive than, say, <strong>Clojure</strong>, <strong>Scheme</strong>, <strong>Erlang/Elixir</strong>, <strong>Haskell</strong>, <strong>C#</strong>, or even <strong>Smalltalk</strong>? Smalltalk has first-class functions and closures, which means that it can do anything JavaScript can do. If you really care about using an expressive language, you’d choose one of the above seven, not a language that is plagued by hobgoblins of every sort and <a href="https://medium.com/javascript-non-grata/javascript-the-next-generation-45b93f1db7fd">apparently one that ECMA TC39 is incapable of fixing</a>.</p><p>So there you have it: the five top reasons to use JavaScript. Good luck with it. You’ll need it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHZFTUtbn1RU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHZFTUtbn1RU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHZFTUtbn1RU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ab33236cf75b77f436d3029bc93f32bc/href">https://medium.com/media/ab33236cf75b77f436d3029bc93f32bc/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd0c0917cf49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/the-five-top-reasons-to-use-javascript-bd0c0917cf49">The Five Top Reasons to Use JavaScript</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Three Big Lies About JavaScript]]></title>
            <link>https://medium.com/javascript-non-grata/the-three-big-lies-about-javascript-e227cabe3beb?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/e227cabe3beb</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Sun, 15 May 2016 04:06:02 GMT</pubDate>
            <atom:updated>2016-05-21T19:12:32.408Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Every lie is two lies — the lie we tell others and the lie we tell ourselves to justify it.<br>~Robert Brault</blockquote><p>There are three big lies that JavaScript fans tell me again and again…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yv0-US42KK9CgnZatwW9QQ.jpeg" /></figure><h4>Lie #1</h4><p><strong>JavaScript is the most misunderstood programming language in the world.</strong> People don’t know how to use it properly and that’s why they get into all kinds of trouble.</p><p>This is a lie because there is <em>nothing</em> special about JavaScript. It is your garden variety imperative/procedural programming language with a smattering of functional programming (FP) capabilities tacked on and a controversial “object-oriented” feature called <em>object prototypes</em>. What is there to misunderstand?</p><p>Basically, the blame for all of JavaScript’s problems is placed on the people using the language: they’re ignorant; they’re lazy; they’re inured to the way programming is done in Java or Python. But what are they ignorant about? Functional programming?</p><p>Why then aren’t people screwing up when using other FP languages such as C#, Clojure, Dart, Elm, Erlang, F#, Julia, Haskell, Scala and Scheme? Functional programming is a fairly well-understood paradigm in the IT industry. So what makes JavaScript especially problematic in this regard?</p><p>Maybe people are ignorant about object prototypes. Read all about <a href="https://medium.com/javascript-non-grata/what-javascripts-object-prototypes-aren-t-807afc9a3203">What JavaScript’s Object Prototypes Aren’t</a>. They aren’t good for proper software engineering. They aren’t a particularly high level of programming abstraction. Prototypes are basically glorified hash tables, quite low level, and what I call the “bricks” for real object-oriented programming (class-based OOP). People may not understand how to use object prototypes, but why would you bother to learn how to lay bricks? It’s not really worth the effort.</p><p>Yes, I get it. Prototypes are flexible. They don’t have all the ceremony that’s behind class-based OOP. In that sense, they’re fun to use. But they don’t scale well for larger applications and that’s why people jump straight to classes. If prototypes were such a useful pattern, you’d see it adopted everywhere else, <strong>because prototypes can be simulated in class-based languages</strong>, just as classes can be simulated in prototype-based languages. And that’s what JavaScript programmers don’t get.</p><h4>Lie #2</h4><p><strong>Asynchronous programming is a key strength of JavaScript.</strong> Well, let’s first understand why asynchronous programming exists in JavaScript at all.</p><p>For graphics user interface (GUI) programming, an event loop is <em>de rigueur</em>, whether it’s in Windows, or X Window, or OS X’s Cocoa, <strong>or the web browser</strong>. They all process user input events asynchronously. Does that mean that asynchronous programming is also a strength of C++ or Objective-C? Event loops (with asynchronous libraries) have been used in Python and Perl and Tcl. I suppose they’re all strong at asynchrony, then? (I laugh when people use the non-existent word “asynchronicity.”)</p><p>So JavaScript uses the event loop and asynchronous processing to support the web browser user interface. This is supposed to make it a great language?</p><p>And now, this model of computing has made Node.js quite popular on the server side where it’s used for non-GUI-related programming, i.e., for high-performance concurrency. Node is obviously useful for many applications, but it’s hardly taking over the world of concurrency. <a href="https://medium.com/javascript-non-grata/the-fall-of-the-house-of-node-43697fd56a6">Recent stories</a> show <a href="https://dzone.com/articles/nodejs-for-enterprise-applications-are-you-kidding"><strong>Node’s limitations</strong></a>. And yet, this is supposed to convince everyone to use JavaScript.</p><blockquote>The event loop has been described as “a poor man’s concurrency.”</blockquote><p>Node proponents like to throw up the same few enterprise examples again and again (PayPal, Netflix, Walmart, Uber, etc.). For every Node example, there are — what? — hundreds of Java examples? Java has proven itself countless times in the enterprise. That’s why it’s practically the industry standard. Node has yet to prove itself. We don’t know how many corporations have tried using Node and gave up on it. We have no idea what the real-world success rate of Node projects is. For an enterprise, choosing Node is still a risky proposition.</p><blockquote>I confidently predict that Go will displace Node in the future once it has grown its ecosystem of frameworks and packages. Its trajectory is undeniable.</blockquote><p>Languages like Go and Erlang/Elixir can easily outperform Node in most concurrency scenarios. The event loop/async model is not sustainable over the long run. We should be attracted to using <em>real</em> concurrent languages if <strong>maximum performance</strong> is our goal. Why compromise with JavaScript?</p><h4>Lie #3</h4><p><strong>JavaScript is the most popular programming language in the world.</strong> Is it really? There is a <strong>huge</strong> difference between a language that is widely used <em>by default</em> and a language that is widely used <em>by choice</em>.</p><blockquote><strong>Remember, in every other application domain besides the web, developers are not held hostage to one language.</strong> We ignore this at our own peril.</blockquote><p>JavaScript is the only language native to the web browser, so it is the most direct means of writing a browser application. Most developers, however, despise the language and <strong>if they really had a choice of a better language, they’d jump to it</strong>. You can see this is true if you search the web (forums, social media, websites, etc.) for opinions about JavaScript. There are numerous long lists of WATs and WTFs for JavaScript that you don’t find for any other language, with the possible exception of PHP. What we know for sure is that <strong>the web is popular, not that JavaScript is popular</strong>.</p><p>Most of the major language ranking indices do not show JavaScript as the most popular. Not even second, third or fourth. IEEE Spectrum says #8, PYPL #5, TIOBE #7, CodeEval #6. Redmonk uses Github statistics which contain a greatly inflated number for JavaScript, precisely because web applications in <em>any</em> language must have at least some JavaScript to work in the browser; there is no choice. So Redmonk cannot give a meaningful ranking for the JavaScript anomaly; otherwise, Java is the most popular language.</p><p>User surveys such as those from StackOverflow also contain similar selection bias. When you have little choice but to use JavaScript for web development, how can you claim it’s a popular language? (Thankfully, however, <a href="https://medium.com/javascript-non-grata/the-super-surrogates-of-javascript-862460199915">transpiled languages are available to us</a>.)</p><p>It behooves us to <a href="https://www.quora.com/Is-it-worth-learning-JavaScript-in-2016/answer/Richard-Eng-1">remember that for all other application domains</a> (e.g., network servers, games and graphics, mobile, desktop, IoT, cloud, etc.), there are plenty of language choices. The web domain is singularly unique. (At least, it is until WebAssembly finally arrives.)</p><h4>The Truth</h4><p>Let me be very clear: <a href="https://medium.com/javascript-non-grata/the-lie-that-has-beguiled-a-generation-of-developers-1b33e82de94f">JavaScript is not a good programming language for software engineering</a>. JavaScript was designed to be a light, breezy scripting language for the web browser. As such, it was made to be flexible and <strong>extremely forgiving</strong>, with <em>weak typing</em> and crazy-ass coercions. It doesn’t even have a proper integer type nor a proper array type. What kind of a language is that?!!</p><p><a href="https://www.quora.com/What-are-the-differences-between-strongly-typed-and-weakly-typed-languages">Weak typing</a> is the Achilles’ Heel of the language for proper software engineering. While it makes writing quick simple scripts for the web browser very easy, it works against you when you’re writing larger applications that require safety and reliability. This is why most major languages are normally <em>strongly typed</em> (not to be confused with statically typed). This is very, very important.</p><p>Weak typing and its consequent freewheeling coercions demonstrate a complete lack of language discipline. This explains a good deal of the numerous WATs and WTFs that plague JavaScript. You can find many online lists of these “warts” but I’ll give you just a few of them here:</p><ul><li><a href="http://wtfjs.com/">http://wtfjs.com/</a></li><li><a href="http://bonsaiden.github.io/JavaScript-Garden/">JavaScript Garden</a></li><li><a href="http://www.codeproject.com/Articles/182416/A-Collection-of-JavaScript-Gotchas">A Collection of JavaScript Gotchas</a></li><li><a href="http://www.javascriptgotchas.com/gotchas/common-javascript-errors-and-mistakes.html">The List of Common JavaScript Gotchas</a></li></ul><p>I’m working very hard to get ECMA TC39 to fix the language’s problems: <a href="https://medium.com/javascript-non-grata/javascript-the-next-generation-45b93f1db7fd">JavaScript: The Next Generation</a>. Alas, I do not hold out much hope.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e227cabe3beb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/the-three-big-lies-about-javascript-e227cabe3beb">The Three Big Lies About JavaScript</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What JavaScript’s Object Prototypes Aren’t]]></title>
            <link>https://medium.com/javascript-non-grata/what-javascripts-object-prototypes-aren-t-807afc9a3203?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/807afc9a3203</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Sun, 08 May 2016 11:33:46 GMT</pubDate>
            <atom:updated>2016-05-09T02:05:08.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ByZVL-Z7BjqGhSBlFKCA-A.jpeg" /></figure><p>I am so sick and tired of hearing JavaScript proponents go on and on about how wonderful object prototypes are, along with prototypal inheritance (whether it’s concatenation or delegation). Let’s set the record straight…</p><p>We’ll begin by remembering why JavaScript was created. Brendan Eich wanted a light, breezy, scripting language for the web browser that was flexible and <strong>forgiving</strong>. It was never intended for serious software engineering. The qualities that make it flexible (e.g, object prototypes and loose typing) are the same qualities that work against good engineering. For all of ECMA TC39’s efforts, this has not changed.</p><p>Think of prototypes as the basic building blocks for an object-oriented programming model. In and of themselves, they are not a particularly high-level abstraction. They are, indeed, light and flexible. This is what makes JavaScript fun and easy to use.</p><p>JavaScript experts like to tout object prototypes as a superior means of doing object-oriented programming (OOP), but the truth is, the IT industry has roundly ignored prototypes, and for good reason. No other notable language created in the past quarter century has adopted object prototypes, except for 23-year-old Lua. The industry has shown a clear preference for class-based OOP, because while classes do have their problems, there is (currently) no better way to organize large-scale application code (say, in the hundreds of thousands of lines). Object prototypes would fall flat on its face here.</p><p>Languages like Smalltalk and C++ are capable of writing programs as big as a million lines of code. JavaScript would be hopeless in these situations. Apparently, ECMA recognized this and tried to accommodate the popularity of classes.</p><p>However, the latest ES6 <em>class</em> feature is only a half-assed implementation of class-based OOP. It’s just syntactic sugar over object prototypes. It still doesn’t support private state (member variables) in the way we expect. Member variables must be “faked” through a variety of workarounds such as programming convention, capturing normal variables with closures, and employing WeakMaps. ES6 is not a proper class-based OOP language like Smalltalk, C++, C# and Java.</p><h4>Conclusion</h4><p>Object prototypes make JavaScript a fun and easy language to use. However, they are not congruent with the goals of software engineering, esp. at scale.</p><p>Leave object prototypes where they belong: as a means of experimenting with ideas and prototyping applications. But when you get down to the brass tacks of engineering, you must use higher level abstractions that help you organize your code better…such as classes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=807afc9a3203" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/what-javascripts-object-prototypes-aren-t-807afc9a3203">What JavaScript’s Object Prototypes Aren’t</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Lie That Has Beguiled A Generation Of Developers]]></title>
            <link>https://medium.com/javascript-non-grata/the-lie-that-has-beguiled-a-generation-of-developers-1b33e82de94f?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/1b33e82de94f</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Tue, 26 Apr 2016 10:59:13 GMT</pubDate>
            <atom:updated>2016-04-29T12:59:15.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*6Bxq9aZS4uYy_-IyBWZXmw.jpeg" /><figcaption>Ruben’s Beguile lady-in-waiting</figcaption></figure><p>It is truly disturbing to see how JavaScript has beguiled the current generation of software developers, esp. on the client side of web development. With the trend toward the Single Page Application (or SPA), along with an uncontrolled proliferation of client-side web frameworks for JavaScript, we are seeing many foolish companies going down the road to software engineering chaos. SPAs are far more complicated to write than traditional server-based applications, eating up more time and resources; the returns are highly questionable. And the web framework landscape is a wild wild West of free-for-alls with most of these frameworks having the life span of a fruit fly. Think Angular, React, Ember, Meteor, Backbone, Knockout, Express, Mithril, Aurelia, etc., etc., etc. <em>Whoa!</em> It would be hilarious if it wasn’t so horrifying. We’ve seen a civil war break out between Angular 1 and 2, and recently witnessed React attempting to upend the JS industry. Who knows how long before React itself is eclipsed.</p><p>On the server side, we’ve seen Node.js gain traction for “back end” applications. But Node has been pretty much relegated to a web niche. ERP solutions like SAP aren’t using Node. While a company may use JS for their website, don’t expect any serious shop to be washing their critical Business Intelligence data through JS code. The truth is, most Fortune 500 shops aren’t basing their businesses on JavaScript <strong>and never will</strong>. Moreover, <a href="https://medium.com/javascript-non-grata/the-fall-of-the-house-of-node-43697fd56a6">we’re starting to see cracks</a> in the usefulness of this runtime environment.</p><p>The reason is simple. JavaScript is intrinsically <a href="https://medium.com/javascript-non-grata/javascript-is-a-dysfunctional-programming-language-a1f4866e186f">a dysfunctional language</a>. It has many more flaws than any other programming language in wide use. JavaScript is wholly unsuitable for serious software engineering, esp. at scale. When your application grows to tens of thousands of lines of code, it becomes much more difficult to maintain, much more difficult to ensure a specific level of quality.</p><p>While JavaScript appears to be spreading well beyond the web UI domain to things like games and graphics, mobile, and the Internet of Things, upon closer inspection the truth is quite revealing. Aside from the little “indie” games you find in app stores and mobiles, no self-respecting game developer is using JavaScript. Hardcore console/PC games like FPSes, RTSes, RPGs, MMOs and up-and-coming VR titles relying on bleeding edge technologies like DX12, Vulkan or Metal will never use JavaScript. The performance requirements are extreme and JS simply cannot deliver.</p><p>For the Internet of Things, there are many well-entrenched languages like Python, Ruby and Perl, and even the ol’ C/C++ standby, available. JS does not have a competitive advantage here.</p><p>In the mobile space, JavaScript won’t be displacing Java, Objective-C and Swift any time soon. Wherever JS can be used outside of the web sphere, better and more solid languages have already staked out the territory. The web browser is really the only place where JavaScript dominates, and even then, its days are numbered. <strong>WebAssembly is coming</strong>, threatening to make JS irrelevant.</p><p>To drive home this point, let’s look at some job statistics. If you compile a list of job postings at Indeed.com for several cities and several languages, here is what you will find (the stats are for April 21, 2016):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*oH1lf-SluPDYO0G1.png" /></figure><p>It is quite evident that JavaScript job postings are nowhere near as plentiful as Java postings, but the more salient fact is this: Nearly all of the JS postings are for “front-end” web developers. Some involve Node. Hardly any are directed at non-web-related activity. If all you want to do is write software for web browsers, then JS may be your ticket, but it’s hardly the path to a rich IT career.</p><p>More job stats can be found at <a href="https://hackerlife.co/blog/language-companies/San-Francisco-Bay-Area-CA">The Hacker Life</a>, which looks at tech jobs in various kinds of companies versus programming languages. For example, in the San Francisco Bay Area, JavaScript is less popular with startups than with older, well-established companies. Startups generally favour Ruby, C and Python. Even the older companies show a greater preference for C++, C#, PHP and Perl! (The results may seem to contradict my look at Indeed, but it must be noted that for The Hacker Life, we don’t know what their data sources nor their methodology are.)</p><p>It is, thus, risible that so many young people are entering the IT industry via the JavaScript route. I see this all the time, everywhere. At Quora, for example, there are endless questions from IT newcomers inquiring about JavaScript. Developer forums such as those at Reddit reveal many new programmers taking online courses from the likes of Free Code Camp and believing that they have a bright future in IT. The JavaScript lie is leading everyone down a garden path.</p><p>No self-respecting Computer Science curriculum teaches JavaScript as a first language. Not the University of Toronto nor the University of California nor MIT. It’s an awful language that teaches you bad habits. So who are these online hucksters peddling JavaScript courses? Do your due diligence.</p><p>Recently, StackOverflow released their <a href="http://stackoverflow.com/research/developer-survey-2016">developer survey</a> which further fuels the JS craze. There are all kinds of selection bias in this report. Its findings are not consistent with most language rankings, which show that JavaScript is hardly eating the world of software. <a href="http://spectrum.ieee.org/computing/software/the-2015-top-ten-programming-languages">IEEE Spectrum</a>, which is based on 12 metrics from 10 data sources, places JavaScript at #8. <a href="http://pypl.github.io/PYPL.html">PYPL</a> puts JavaScript in #5 position. <a href="http://www.tiobe.com/tiobe_index?page=index">TIOBE</a> says JavaScript is at #7. <a href="http://blog.codeeval.com/codeevalblog/2016/2/2/most-popular-coding-languages-of-2016">CodeEval</a> ranks it as #6.</p><p>Even <a href="http://redmonk.com/sogrady/2016/02/19/language-rankings-1-16/">Redmonk</a>’s language ranking is deceptive. JavaScript is on top because of the massive number of lines of code committed to Github. What are we to make of this? Well, since JS is the only language native to web browsers, any web project in any language must have some JS code. The number of lines of code for JS is greatly inflated when all of these projects are committed to Github. JS is not used by choice, and Redmonk proves that the web is popular, not that JS is popular. <em>Duh!</em></p><p>Lest you think I’m all about tearing down the language, I am also about <em>reforming</em> the language. Read <a href="https://medium.com/javascript-non-grata/javascript-the-next-generation-45b93f1db7fd">my plan</a> for JavaScript.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/lie-has-beguiled-generation-developers-richard-eng"><em>www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b33e82de94f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/the-lie-that-has-beguiled-a-generation-of-developers-1b33e82de94f">The Lie That Has Beguiled A Generation Of Developers</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is JavaScript the Most Common Language in the World?]]></title>
            <link>https://medium.com/javascript-non-grata/is-javascript-the-most-common-language-in-the-world-ca645175c134?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/ca645175c134</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Mon, 18 Apr 2016 04:07:31 GMT</pubDate>
            <atom:updated>2016-04-29T17:56:37.972Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*LWbnVbRPbZLrIw0arAZOdw.jpeg" /></figure><p>Daniel Rowinski, Editor-in-Chief at ARC (Application Resource Center) from Applause, wrote an outrageous editorial proclaiming that, “<a href="https://arc.applause.com/2016/03/22/javascript-is-the-worlds-dominant-programming-language/">It’s Official: JavaScript Is The Most Commonly Used Programming Language On Earth</a>.”</p><p>This is such an overwrought conclusion. StackOverflow’s developer survey is just one metric. It may well be anomalous. It is certainly open to interpretation and critique (for example, <a href="https://medium.com/@glitterwitch/stack-overflow-s-developer-survey-analysis-hurts-women-ec4d568e2352#.iesh4pvbj">“survey analysis hurts women”</a>). The survey purports to reach a whopping 0.4% of all developers around the globe. This is absolutely stunning. Not.</p><p>Extrapolating from 56,000 developers to glean some kind of insight for over 14 million people is quite a reach. For one thing, we don’t know what types of developers choose to participate in the survey and what types decline (for whatever reason). There are undoubtedly a few kinds of selection bias built into the survey.</p><p>We also know polls and surveys are unreliable. They don’t tell the whole story. Political polls, for example, have poor predictive power and are frequently wrong. Polls, and the StackOverflow survey, provide interesting indicators that can help guide you, but you shouldn’t make important decisions based on just one survey.</p><p>The truth is that most language rankings do not place JavaScript on top. <a href="http://spectrum.ieee.org/computing/software/the-2015-top-ten-programming-languages">IEEE Spectrum</a>, which is based on 12 metrics from 10 data sources, places JavaScript at #8. <a href="http://pypl.github.io/PYPL.html">PYPL</a> puts JavaScript in #5 position. <a href="http://www.tiobe.com/tiobe_index?page=index">TIOBE</a> says JavaScript is at #7. <a href="http://blog.codeeval.com/codeevalblog/2016/2/2/most-popular-coding-languages-of-2016">CodeEval</a> ranks it as #6.</p><p>And consider this: web development is the hottest technology today. JavaScript is the native language of the web browser, so if you want to develop for the web, what choice do you have? It doesn’t make JavaScript “popular.” It makes it an unfortunate necessity; you simply have to hold your nose. In truth, though, <a href="https://medium.com/javascript-non-grata/the-super-surrogates-of-javascript-862460199915">you do have choices</a>.</p><p><a href="http://redmonk.com/sogrady/2016/02/19/language-rankings-1-16/">Redmonk</a>’s language rankings are based on StackOverflow and Github numbers, too. JavaScript is on top because the number of lines of code committed to Github is a staggering 4 billion. (The number is greatly inflated by web projects in other languages; when you commit them to Github, you also commit a measure of JS code.) <em>We have always known this</em>, and it ought not to be surprising: web applications rely on JavaScript, and most people do not deliberately use JavaScript by choice. The choice is made for them. Sane people do not choose <a href="https://medium.com/javascript-non-grata/javascript-is-a-dysfunctional-programming-language-a1f4866e186f">a broken language</a>.</p><p>To be sure, many, many, <em>many</em> JS programmers ask questions on StackOverflow. This also should not be surprising. JavaScript is so perplexing that flummoxed newcomers naturally gravitate to the most common programmer resource available. In fact, this understanding was one of the foundations for Seerene’s controversial study released just two weeks ago: <a href="http://betanews.com/2016/04/04/most-complex-programming-language/">Which is the most complex programming language?</a> (JavaScript!)</p><p>Also, <a href="https://hackerlife.co/blog/language-companies/San-Francisco-Bay-Area-CA">The Hacker Life</a> presents some interesting analysis about tech jobs in various kinds of companies versus programming languages. For example, in the San Francisco Bay Area, JavaScript is less popular with startups than with older, well-established companies. Startups generally favour Ruby, C, and Python. Even the older companies show a greater preference for C++, C#, PHP, and Perl! At least in the job market, JavaScript is nowhere near the most popular.</p><p>There is absolutely nothing “official” about Mr. Rowinski’s thesis. It is simply hyperbolic ignorance masquerading as intelligent insight. The best we can say is that StackOverflow’s survey is an interesting data point. We must, however, look for confirmation and good judgment to go with it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca645175c134" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/is-javascript-the-most-common-language-in-the-world-ca645175c134">Is JavaScript the Most Common Language in the World?</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript is the Most Complex Programming Language]]></title>
            <link>https://medium.com/javascript-non-grata/javascript-is-the-most-complex-programming-language-fc68cfb234bb?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc68cfb234bb</guid>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Wed, 13 Apr 2016 13:45:36 GMT</pubDate>
            <atom:updated>2016-04-13T14:35:50.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*IFp3WjkcG8Uf1ttLnfQuFw.jpeg" /></figure><p>Not surprisingly, this is consistent with my finding that <a href="https://medium.com/smalltalk-talk/smalltalk-s-proven-productivity-fe7cbd99c061">JavaScript is one of the least productive programming languages</a> (faring worse than C++ and Java!).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc68cfb234bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/javascript-is-the-most-complex-programming-language-fc68cfb234bb">JavaScript is the Most Complex Programming Language</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript: The Next Generation]]></title>
            <link>https://medium.com/javascript-non-grata/javascript-the-next-generation-45b93f1db7fd?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/45b93f1db7fd</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Mon, 11 Apr 2016 04:10:06 GMT</pubDate>
            <atom:updated>2017-01-02T14:37:33.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYacICS_BmT99ly8MplyZQ.png" /><figcaption>The Next Generation Enterprise</figcaption></figure><h4>How to Fix JavaScript and Learn to Love Web Development</h4><p>Python did it, moving from version 2.7 to 3. PHP did it, moving from version 5.6 to 7. Perl did it, moving from version 5.22 to 6. What did they all do?</p><p>They fixed their language’s most egregious faults by making <em>breaking changes</em>. Why doesn’t ECMA do the same with JavaScript?</p><p>After all, <a href="https://medium.com/javascript-non-grata/javascript-is-a-dysfunctional-programming-language-a1f4866e186f">JavaScript is essentially a broken language</a>. Using it is like having <a href="https://medium.com/javascript-non-grata/javascript-s-sword-of-damocles-47256cf17b5a">the Sword of Damocles hanging over your head</a>. It is most disconcerting that <em>this inferior software engineering tool</em> is metastasizing into nearly every corner of IT, from web to server, desktop, mobile, IoT, cloud, games, etc. We should at least give everyone a more solid foundational language.</p><p>Just like Python, ECMA should repair <strong>the basic, fundamental flaws</strong> in JavaScript, instead of piling on new features. It should eliminate all the WATs and WTFs that have so plagued the language and <a href="https://medium.com/javascript-non-grata/down-the-javascript-hole-f45417ce7d1f">made it a laughing stock</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FD5xh0ZIEUOE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DD5xh0ZIEUOE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FD5xh0ZIEUOE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/98ea1dffb57684f7fb9d847cff7ec834/href">https://medium.com/media/98ea1dffb57684f7fb9d847cff7ec834/href</a></iframe><p>Fear of short-term turmoil in the web community should not deter ECMA, just as fear of disruption in the Python community <a href="https://youtu.be/rTTFh7HOlC0?t=9m22s">did not deter Guido van Rossum</a>.</p><p>ECMA can start by instituting something similar to “use strict;”, say, “use nextgen;”. <strong>Jettison all the baggage</strong> from JavaScript, things like loose typing and freewheeling coercions, the confusing “==” vs “===”, the lack of an integer type, the lack of a proper array type, the dysfunctional “typeof” and “instanceof”, the confusing “this”, and so on. Make JavaScript clean and consistent.</p><p>Over time, ECMA can encourage browser makers to adopt the new JavaScript and encourage JS library authors to make their libraries polyglot. It should have a solid migration plan, along with a good marketing plan, to accelerate the transition–it’s better to quickly yank off the Band-Aid than to slowly pull it off. The JS community needs to stand behind the new JavaScript (and I’ll be most happy to join the marketing team). There will inevitably be a period of disruption, but in the long run, it’ll be worth it. <strong>This is absolutely doable.</strong></p><p>It requires courage. It’s a simple decision: “short-term pain for long-term gain.” Just bite the bullet and <strong>do it</strong>. Give us the <strong><em>Next Generation JavaScript</em></strong><em>.</em></p><p>Otherwise, JavaScript risks irrelevancy once WebAssembly finally arrives.</p><p>Please, <a href="https://medium.com/javascript-non-grata/an-open-letter-to-ecma-cb60ee917da9">no more putting lipstick on a pig</a>.</p><p>Some people may ask: <em>Why go to all this trouble just to eliminate things from the language that can be avoided through the use of ESLint*, and self-discipline, and proper education?</em> Here’s the problem…</p><p>The majority of JavaScript developers today have not received the proper education and do not exercise enough self-discipline to use JavaScript well. One only needs to look at the numerous JavaScript libraries that are available. Some are well-written; most are atrocious. These were all written by the current generation of JavaScript programmers, most of whom clearly do not know how to use best practices. <a href="https://medium.com/javascript-scene/javascript-training-sucks-284b53666245">Eric Elliott has lamented about this</a>, saying that as few as one in a hundred know what the hell they’re doing!</p><p>Every day, more and more novice programmers are joining the ranks of JavaScript developers. Many are self-taught, or have taken online courses that don’t really go very far beyond the basics. And don’t forget David Flanagan’s standard bearer, “JavaScript: The Definitive Guide,” which continues to teach people all of JavaScript’s ugly features. How are they learning the best practices?</p><p>Even Douglas Crockford’s “JavaScript: The Good Parts” doesn’t help. I’ve heard complaints about some of Crockford’s recommendations. Not everyone reads his book, and not everyone follows his prescription. It’s just too easy to fall back to The Definitive Guide and use the rest of JavaScript.</p><p>The point is that the JavaScript community is growing by leaps and bounds, and the general level of skillfulness is very low. While this complaint can be levelled against other languages such as Java and Python, the situation is greatly exacerbated by the language’s own dysfunctional nature. <em>Can we at least take this impediment out of the equation?</em> Is that really asking too much?</p><p>Let’s make the <strong><em>Next Generation JavaScript</em></strong> the very best language we can envision. Let’s finally make web development a proper engineering discipline and love it! Make your voice heard at ECMA. Shout it out to your colleagues. Be vociferous in the blogosphere. <a href="https://www.youtube.com/watch?v=sZt6eU5REN8"><strong><em>Make it so</em></strong></a><strong><em>!</em></strong></p><p>* Linters can also produce <em>false positives</em> which cause you to look for phantom problems. This can be a real time-waster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45b93f1db7fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/javascript-the-next-generation-45b93f1db7fd">JavaScript: The Next Generation</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Down The JavaScript Hole]]></title>
            <link>https://medium.com/javascript-non-grata/down-the-javascript-hole-f45417ce7d1f?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/f45417ce7d1f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Fri, 01 Apr 2016 12:36:44 GMT</pubDate>
            <atom:updated>2016-04-01T12:36:50.722Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="http://cube-drone.com/comics/c/relentless-persistence"><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*sEgImulGWlLP62uWqi5LlA.png" /></a></figure><p>Best to stay out of the hole. Welcome to <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f45417ce7d1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/down-the-javascript-hole-f45417ce7d1f">Down The JavaScript Hole</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript is a Dysfunctional Programming Language]]></title>
            <link>https://medium.com/javascript-non-grata/javascript-is-a-dysfunctional-programming-language-a1f4866e186f?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/a1f4866e186f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Wed, 16 Mar 2016 14:25:32 GMT</pubDate>
            <atom:updated>2016-10-09T02:18:40.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*edif3fw6GtVWUogRaeuYoQ.jpeg" /></figure><p>JavaScript is supposedly a <em>functional</em> programming language. (Actually, it’s multi-paradigm, mainly imperative with some functional capabilities and a smattering of object orientation, via object prototypes.) Unfortunately, JavaScript is also a <strong><em>dys</em></strong><em>functional</em> programming language, imbued with a myriad of “warts” and “gotchas.” It lacks the discipline to be a serious software engineering language, thanks to loose typing and freewheeling coercions, and their wildly inconsistent semantics. JavaScript doesn’t even have a proper integer type! <a href="https://youtu.be/D5xh0ZIEUOE">JavaScript also doesn’t have a proper array type</a> like you find in most normal programming languages. Just to be clear, <a href="https://medium.com/javascript-non-grata/an-open-letter-to-ecma-cb60ee917da9">despite ECMA working hard to fix JavaScript</a>, it has yet to address the abovementioned problems.</p><p>JavaScript apologists are constantly telling us that all programming languages have warts. What they don’t tell us is that most languages have <strong>far fewer warts</strong> than JavaScript has. How big is the problem for this language? The following graphic gives you some idea:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kd0UGiDvgooFooCy28rs8Q.jpeg" /></figure><p>Here are some long lists of warts:</p><ul><li><a href="http://wtfjs.com/">wtfjs</a></li><li><a href="http://bonsaiden.github.io/JavaScript-Garden/">JavaScript Garden</a></li><li><a href="http://www.codeproject.com/Articles/182416/A-Collection-of-JavaScript-Gotchas">JavaScript Gotchas</a></li><li><a href="http://www.javascriptgotchas.com/gotchas/common-javascript-errors-and-mistakes.html">Common JavaScript Errors</a></li></ul><p>Are there similarly long lists for Java or Python?</p><p>These same apologists also tell us that by applying good practices, including linters*, you can avoid the bad parts, and you’re left with programming joy. Isn’t that what Douglas Crockford’s book is all about? This is a fairy tale, of course. Good practices are not a perfect solution. Sooner or later, JavaScript’s loose typing and inconsistent semantics will bite you in the ass. Sooner or later, the lack of integers or proper array type will prove annoying. These things are like land mines, laying in wait with infinite patience to blow off your legs. Good practices <em>mitigate</em> but do not <em>eliminate</em> the problems.</p><p>(* Linters can also produce <em>false positives</em> which cause you to look for phantom problems. This can be a real time-waster.)</p><p>The need to be constantly aware of the bad parts most definitely places an added and unnecessary cognitive burden on the programmer. I alluded to this in <a href="https://medium.com/javascript-non-grata/javascript-s-sword-of-damocles-47256cf17b5a">JavaScript’s Sword of Damocles</a>. So why do JavaScript proponents continue to promote its use?</p><p>The answer is: JavaScript’s large user community and ecosystem of tools and libraries, not to mention the large number of jobs available for JavaScript developers. This answer also explains the longevity of all the mainstream languages, irrespective of their faults, including: PHP, C++, Perl, and Visual Basic (languages everybody loves to hate).</p><p>The community and ecosystem argument is certainly quite compelling. There is no doubt that these things confer substantial benefits for both businesses and programmers. The benefits, however, must be balanced against the downsides, such as:</p><ul><li>the complexity and difficulty of maintaining the code base as the application grows beyond the safe threshold for the language (in the case of JavaScript, I’d say that’s about 20k LOC)</li><li>the diminished reliability of the software as it grows so big that JavaScript’s lack of discipline interferes with the ability to ferret out defects and prove program correctness</li><li>the difficulty of delivering software on time and on budget because the language imposes an unpleasant cognitive burden and slows down the programmer’s pace of work (<a href="https://smalltalkrenaissance.wordpress.com/2015/02/16/smalltalks-proven-productivity/">a scientific study</a> has shown JavaScript to be one of the <strong>least productive</strong> languages in IT, well behind C++, Java, and C#)</li></ul><p>In other words, this is <strong>user community</strong>, <strong>ecosystem</strong>, and <strong>jobs</strong> versus <strong>maintainability</strong>, <strong>reliability</strong>, and <strong>productivity</strong>. The classical contention in IT.</p><p>It must be noted that while a rich ecosystem does aid in productivity (with reusable code, there’s no need to reinvent the wheel), you must still write new code for your business logic, UI design, testing procedures, etc. An inefficient language can hamper the latter to the extent that it wipes out the ecosystem advantage. A powerful and elegant language can work miracles. A prime example of this is <a href="https://medium.com/smalltalk-talk">Smalltalk</a>. This language is much vaunted for its extremely high productivity, thanks to an incredible “live” programming IDE/debugger, and to impossibly clean syntax and semantics which remove any cognitive burden. In other words, Smalltalk <em>gets out of your way</em> so that you can focus on writing your application in the most efficient manner. This makes for a very pleasant programming experience, almost zen-like! Smalltalk’s ecosystem is not nearly as rich as JavaScript’s, but <a href="https://medium.com/smalltalk-talk/smalltalk-vs-javascript-f35e8bcc5ef4">I wouldn’t bet against Smalltalk</a> in any programming contest.</p><blockquote><em>We are like Samson pushing back on the spurious promises of JavaScript, the lie that has beguiled a generation of naive developers. How do you counter so many foolish minds?</em></blockquote><p>There’s no denying that JavaScript is very useful. Many modest-size applications have been written. The area where I am most concerned with is in <em>software engineering at scale</em>…applications that are many tens of thousands of lines of code (or LOC) long.</p><p>Of course, you can use any language to write large-scale applications. The question is, what are the risks involved? How much additional effort is required?</p><p>There may well be some large applications written in JavaScript (I don’t actually know), but this doesn’t tell us the whole story. It doesn’t tell us how reliable the software is, how many defects there are. How much down time did the application suffer? It doesn’t tell us how maintainable the code base is over time. It doesn’t tell us the life cycle cost of using JavaScript, which <a href="https://smalltalkrenaissance.wordpress.com/2015/02/16/smalltalks-proven-productivity/">this study suggests is very bad</a>. These are all real costs that cannot be ignored. Businesses are loathe to reveal such information.</p><p>From the enterprise perspective, we know that it’s safer to use Java, C#, C++, Python, etc. These languages rest on a solid foundation. They are proven quantities. They don’t have Bad Parts that far outweigh the Good Parts. This is a question of <strong>trust</strong>.</p><p>Ultimately, the question comes down to this: <strong>Are you doing serious software engineering, or are you hacking together relatively simple applications (less than 20k LOC)?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1f4866e186f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/javascript-is-a-dysfunctional-programming-language-a1f4866e186f">JavaScript is a Dysfunctional Programming Language</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Super Surrogates of JavaScript]]></title>
            <link>https://medium.com/javascript-non-grata/the-super-surrogates-of-javascript-862460199915?source=rss----3fcce414cbc9---4</link>
            <guid isPermaLink="false">https://medium.com/p/862460199915</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[smalltalk]]></category>
            <dc:creator><![CDATA[Richard Kenneth Eng]]></dc:creator>
            <pubDate>Wed, 02 Mar 2016 15:11:44 GMT</pubDate>
            <atom:updated>2018-04-24T19:18:21.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckN0Y27Uxk92sw-r4Ut6Uw.jpeg" /><figcaption>JS-diss League of America, by JPRart at DeviantArt</figcaption></figure><p>There are at least two important things we know for certain about the popular programming language JavaScript:</p><ol><li>JavaScript is the native language in web browsers. Thus, we cannot escape from using it in web development.</li><li>JavaScript has a great many “warts” and <a href="https://medium.com/javascript-non-grata/javascript-s-sword-of-damocles-47256cf17b5a">semantical inconsistencies</a>, much more so than in other programming languages. It’s not only <em>slightly</em> worse than other languages; <a href="https://medium.com/javascript-non-grata/samson-and-javascript-3ff39a4f836d">it is substantively <em>much</em> worse</a>. So much so that a book had to be written to guide you through the “Good Parts.”</li></ol><p>That being said, there is absolutely no solid rationale to <em>directly</em> program in JavaScript. The language can be used as a <em>transpiler target</em> for other languages that have a more solid foundation. In fact, there is <a href="https://github.com/jashkenas/coffeescript/wiki/list-of-languages-that-compile-to-js">an embarrassment of riches</a> to choose from.</p><p>Here are several examples of transpiled languages and their best representative web applications…</p><h4><a href="http://amber-lang.net/">Amber</a> (Smalltalk)</h4><p>Smalltalk is a pure object-oriented programming (OOP) language that has an impossibly clean and simple syntax. In fact, it is widely regarded as the grandfather of OOP languages having influenced numerous other OOP languages, and yet <a href="https://medium.com/smalltalk-talk">it remains fresh and modern today</a>. With Amber, <a href="https://medium.com/smalltalk-talk/a-gentle-introduction-to-amber-8c532631e9ab">Smalltalk is ready for the web</a>. (In Amber, JavaScript objects from JS libs are treated just like Smalltalk objects! How cool is that?)</p><figure><a href="https://www.multicity-carsharing.de/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVbWgpBy7LUn5MLms0etHA.png" /></a></figure><h4><a href="http://brython.info/">Brython</a> (Python)</h4><figure><a href="http://www.ifsc.usp.br/~htpoligo/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sEVG04K9hf1oD8Z4hM3Pkw.png" /></a></figure><h4><a href="https://github.com/clojure/clojurescript">ClojureScript</a> (Clojure)</h4><p>Clojure is a dialect of Lisp (commonly regarded as the grandfather of functional programming, or FP, languages) that runs atop the JVM. It also has a clean and elegant syntax. ClojureScript gives Clojure a strong web presence.</p><figure><a href="https://racehubhq.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k_p-hkYF-wB65e7Idl4jOw.png" /></a></figure><h4><a href="https://www.dartlang.org/">Dart</a></h4><p>Dart is <a href="https://medium.com/p/dart-is-dead-aedced9fd3d1">Google’s failed attempt to overtake JavaScript</a>, but it remains a good tool for web development.</p><figure><a href="http://www.biborg.com/case-studies/netflix/marvels-daredevil/digital-out-of-home/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crW7AWqC_ZTEbnjFWXtf2Q.png" /></a></figure><h4><a href="http://www.gopherjs.org/">GopherJS</a> (Go)</h4><p>Go is a concurrent programming language with a simple syntax and a minimalist, orthogonal and powerful feature set. Despite its controversial nature, <a href="https://medium.com/p/the-little-language-that-could-61eaa62b5e0a">it has recently become very popular</a>. GopherJS lets you use this marvelous language for front-end web development. I strongly encourage you to install GopherJS and run the following web app to see how easy it is:</p><figure><a href="https://github.com/gopherjs/todomvc"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhPCTBqf9egsxkVMXo2Nnw.png" /></a></figure><h4><a href="http://www.gwtproject.org/">GWT</a> (Java)</h4><figure><a href="https://www.cloudorado.com/cloud_server_comparison.jsp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCARhYTvrxPXiwU5VczLzQ.png" /></a></figure><h4><a href="http://haxe.org/">Haxe</a></h4><p>Haxe is a remarkable language that can transpile to several different platforms, including ActionScript 3, JavaScript, Java, C#, C++, and PHP.</p><figure><a href="http://netwars-project.com/webdoc"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Sw2QxzgjkO46TuzzHlO6A.png" /></a></figure><h4><a href="http://www.scala-js.org/">Scala.js</a> (Scala)</h4><figure><a href="https://www.theseventhsense.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4HQ19zKIkTLczN7JM-IGw.png" /></a></figure><p>These examples demonstrate the efficacy of using a transpiled language for your web development. You need not inflict a broken language on yourself. JavaScript was originally designed as an off-the-cuff scripting language for web browsers. It was never intended for serious software engineering and <a href="https://medium.com/javascript-non-grata/an-open-letter-to-ecma-cb60ee917da9">no matter how much ECMA try to spruce up the language</a>, <strong>without fixing its basic, fundamental problems</strong>, JavaScript remains unsuitable for writing industrial strength software. Loose typing and freewheeling coercions, silent runtime failures due to bad syntax, and lack of a proper number type are anathema to complex programming. If you want a fun, light language to do relatively simple tasks, JS is fine, but let’s not pretend it can compete with the likes of Go, C#, Java, Python, C++, etc.</p><p>Honourable mentions go to <a href="http://bridge.net/">Bridge.NET</a> (C#), <a href="http://leaningtech.com/cheerp/">Cheerp</a> (C++), <a href="http://yosbelms.github.io/cor/">Cor</a>, <a href="http://elm-lang.org/">Elm</a>, <a href="https://kotlinlang.org/">Kotlin</a>, <a href="https://opalrb.com/">Opal</a> (Ruby), and <a href="http://www.transcrypt.org/">Transcrypt</a> (Python). They’re worth exploring.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=862460199915" width="1" height="1" alt=""><hr><p><a href="https://medium.com/javascript-non-grata/the-super-surrogates-of-javascript-862460199915">The Super Surrogates of JavaScript</a> was originally published in <a href="https://medium.com/javascript-non-grata">JavaScript Non Grata</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>