<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why is the source code of JavaScript apps transmitted to the browser? in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/why-is-the-source-code-of-javascript-apps-transmitted-to-the/m-p/48002#M17144</link>
    <description>&lt;P&gt;Why is the source code of JavaScript apps transmitted to the browser where:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;It is much larger than an equivalent executable p-code, which increases the delivery time, and requires the browser to compile the code before interpreting it.&lt;/LI&gt;&lt;LI&gt;It exposes proprietary information of the authors&lt;/LI&gt;&lt;LI&gt;It is useless to anyone except the developers.&amp;nbsp; End users cannot use it for debugging.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;The industry has standardized on many capabilities.&amp;nbsp; Why could it not standardize on a common virtual machine representation which could be either interpreted or run through a JIT compiler. We do not transmit Java, or C#, or WASM source to the browser, so why is JavaScript different?&amp;nbsp; What is the advantage to the &lt;STRONG&gt;Industry&lt;/STRONG&gt; of continuing to transmit source as if it was still 1995?&amp;nbsp; Note that I wrote my first web site in 1992, including server code using the CGI interface on the original NCSC HTTPD.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Dec 2023 21:42:43 GMT</pubDate>
    <dc:creator>jamescobban_net</dc:creator>
    <dc:date>2023-12-27T21:42:43Z</dc:date>
    <item>
      <title>Why is the source code of JavaScript apps transmitted to the browser?</title>
      <link>https://connect.mozilla.org/t5/discussions/why-is-the-source-code-of-javascript-apps-transmitted-to-the/m-p/48002#M17144</link>
      <description>&lt;P&gt;Why is the source code of JavaScript apps transmitted to the browser where:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;It is much larger than an equivalent executable p-code, which increases the delivery time, and requires the browser to compile the code before interpreting it.&lt;/LI&gt;&lt;LI&gt;It exposes proprietary information of the authors&lt;/LI&gt;&lt;LI&gt;It is useless to anyone except the developers.&amp;nbsp; End users cannot use it for debugging.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;The industry has standardized on many capabilities.&amp;nbsp; Why could it not standardize on a common virtual machine representation which could be either interpreted or run through a JIT compiler. We do not transmit Java, or C#, or WASM source to the browser, so why is JavaScript different?&amp;nbsp; What is the advantage to the &lt;STRONG&gt;Industry&lt;/STRONG&gt; of continuing to transmit source as if it was still 1995?&amp;nbsp; Note that I wrote my first web site in 1992, including server code using the CGI interface on the original NCSC HTTPD.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Dec 2023 21:42:43 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/why-is-the-source-code-of-javascript-apps-transmitted-to-the/m-p/48002#M17144</guid>
      <dc:creator>jamescobban_net</dc:creator>
      <dc:date>2023-12-27T21:42:43Z</dc:date>
    </item>
  </channel>
</rss>

