<story><title>JavaScript at 20</title><url>http://brendaneich.github.io/ModernWeb.tw-2015/</url></story><parent_chain><item><author>teacup50</author><text>There are no end of alternatives out there today, from mobile platforms to research languages exploring a myriad of aspects of computer science.&lt;p&gt;Just let me know when browser vendors are going to break down the two-tiered system, and let us run the legion of alternatives alongside -- instead of under -- JavaScript.&lt;p&gt;Or, they could take their own medicine, and try and write the browser in JS.</text></item><item><author>knightofmars</author><text>&amp;quot;Haters gonna hate.&amp;quot;  Anyone claiming that JS is the &amp;quot;worst thing to happen to the web&amp;quot; and&amp;#x2F;or that some other language would miraculously solve all of the problems present in JS should do the following, &amp;quot;Go create it.&amp;quot;  Don&amp;#x27;t whine about the barriers and how a new language would never be adopted because &amp;quot;JS is already everywhere.&amp;quot;  There are plenty of people already trying to solve this problem by actively doing something.  I&amp;#x27;ve worked with enough engineers that love to criticize every design choice made but when it comes to asking them what the better alternative is they have nothing to say.  They just &amp;quot;know&amp;quot; there&amp;#x27;s a better way.  Well, stop using your intuition based rationalizing that there&amp;#x27;s a problem and start using your creative and logical faculties to actually solve the &amp;quot;perceived&amp;quot; problem before presenting a criticism.  Or at a minimum present a well thought out and actionable direction towards the solution.</text></item></parent_chain><comment><author>pcwalton</author><text>&amp;gt; Just let me know when browser vendors are going to break down the two-tiered system, and let us run those myriad of alternatives alongside -- instead of under -- JavaScript.&lt;p&gt;The complexity of doing that would be needlessly high compared to just improving JavaScript. Having to integrate a C++ DOM with a JS DOM is hard enough. Think about how you handle cross-language cycles…&lt;p&gt;&amp;gt; Or, they could take their own medicine, and try and write the browser in JS.&lt;p&gt;You mean like Firefox?</text></comment>
<story><title>JavaScript at 20</title><url>http://brendaneich.github.io/ModernWeb.tw-2015/</url></story><parent_chain><item><author>teacup50</author><text>There are no end of alternatives out there today, from mobile platforms to research languages exploring a myriad of aspects of computer science.&lt;p&gt;Just let me know when browser vendors are going to break down the two-tiered system, and let us run the legion of alternatives alongside -- instead of under -- JavaScript.&lt;p&gt;Or, they could take their own medicine, and try and write the browser in JS.</text></item><item><author>knightofmars</author><text>&amp;quot;Haters gonna hate.&amp;quot;  Anyone claiming that JS is the &amp;quot;worst thing to happen to the web&amp;quot; and&amp;#x2F;or that some other language would miraculously solve all of the problems present in JS should do the following, &amp;quot;Go create it.&amp;quot;  Don&amp;#x27;t whine about the barriers and how a new language would never be adopted because &amp;quot;JS is already everywhere.&amp;quot;  There are plenty of people already trying to solve this problem by actively doing something.  I&amp;#x27;ve worked with enough engineers that love to criticize every design choice made but when it comes to asking them what the better alternative is they have nothing to say.  They just &amp;quot;know&amp;quot; there&amp;#x27;s a better way.  Well, stop using your intuition based rationalizing that there&amp;#x27;s a problem and start using your creative and logical faculties to actually solve the &amp;quot;perceived&amp;quot; problem before presenting a criticism.  Or at a minimum present a well thought out and actionable direction towards the solution.</text></item></parent_chain><comment><author>ender7</author><text>Chrome was trying to do this: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;developer.chrome.com&amp;#x2F;native-client&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;developer.chrome.com&amp;#x2F;native-client&lt;/a&gt;&lt;p&gt;However, cries of foul &amp;quot;vendor lockin&amp;quot; erupted. So I dunno what to tell you, man.</text></comment>