Putting in All the Stops: Execution Control for JavaScript

Scores of compilers produce JavaScript, enabling programmers to use many languages on the Web, reuse existing code, and even use Web IDEs. Unfortunately, most compilers inherit the browser's compromised execution model, so long-running programs freeze the browser tab, infinite loops crash IDEs,...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:arXiv.org 2018-04
Hauptverfasser: Baxter, Samuel, Nigam, Rachit, Joe Gibbs Politz, Krishnamurthi, Shriram, Guha, Arjun
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page
container_issue
container_start_page
container_title arXiv.org
container_volume
creator Baxter, Samuel
Nigam, Rachit
Joe Gibbs Politz
Krishnamurthi, Shriram
Guha, Arjun
description Scores of compilers produce JavaScript, enabling programmers to use many languages on the Web, reuse existing code, and even use Web IDEs. Unfortunately, most compilers inherit the browser's compromised execution model, so long-running programs freeze the browser tab, infinite loops crash IDEs, and so on. The few compilers that avoid these problems suffer poor performance and are difficult to engineer. This paper presents Stopify, a source-to-source compiler that extends JavaScript with debugging abstractions and blocking operations, and easily integrates with existing compilers. We apply Stopify to 10 programming languages and develop a Web IDE that supports stopping, single-stepping, breakpointing, and long-running computations. For nine languages, Stopify requires no or trivial compiler changes. For eight, our IDE is the first that provides these features. Two of our subject languages have compilers with similar features. Stopify's performance is competitive with these compilers and it makes them dramatically simpler. Stopify's abstractions rely on first-class continuations, which it provides by compiling JavaScript to JavaScript. We also identify sub-languages of JavaScript that compilers implicitly use, and exploit these to improve performance. Finally, Stopify needs to repeatedly interrupt and resume program execution. We use a sampling-based technique to estimate program speed that outperforms other systems.
format Article
fullrecord <record><control><sourceid>proquest</sourceid><recordid>TN_cdi_proquest_journals_2072000370</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2072000370</sourcerecordid><originalsourceid>FETCH-proquest_journals_20720003703</originalsourceid><addsrcrecordid>eNqNjUEKwjAQAIMgWLR_WPBciBtrpTcpFfEk1HspJdWUkK3JRny-PfgAT3OYgVmIBJXaZcc94kqkIYxSSjwUmOcqEeUtMhv3AOPgZC3wU0PDNIUS6o_uIxtyUJFjTxYG8nDt3l3TezPxRiyHzgad_rgW23N9ry7Z5OkVdeB2pOjdrFqUBc5XVUj1X_UFeMk2Kw</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>2072000370</pqid></control><display><type>article</type><title>Putting in All the Stops: Execution Control for JavaScript</title><source>Free E- Journals</source><creator>Baxter, Samuel ; Nigam, Rachit ; Joe Gibbs Politz ; Krishnamurthi, Shriram ; Guha, Arjun</creator><creatorcontrib>Baxter, Samuel ; Nigam, Rachit ; Joe Gibbs Politz ; Krishnamurthi, Shriram ; Guha, Arjun</creatorcontrib><description>Scores of compilers produce JavaScript, enabling programmers to use many languages on the Web, reuse existing code, and even use Web IDEs. Unfortunately, most compilers inherit the browser's compromised execution model, so long-running programs freeze the browser tab, infinite loops crash IDEs, and so on. The few compilers that avoid these problems suffer poor performance and are difficult to engineer. This paper presents Stopify, a source-to-source compiler that extends JavaScript with debugging abstractions and blocking operations, and easily integrates with existing compilers. We apply Stopify to 10 programming languages and develop a Web IDE that supports stopping, single-stepping, breakpointing, and long-running computations. For nine languages, Stopify requires no or trivial compiler changes. For eight, our IDE is the first that provides these features. Two of our subject languages have compilers with similar features. Stopify's performance is competitive with these compilers and it makes them dramatically simpler. Stopify's abstractions rely on first-class continuations, which it provides by compiling JavaScript to JavaScript. We also identify sub-languages of JavaScript that compilers implicitly use, and exploit these to improve performance. Finally, Stopify needs to repeatedly interrupt and resume program execution. We use a sampling-based technique to estimate program speed that outperforms other systems.</description><identifier>EISSN: 2331-8422</identifier><language>eng</language><publisher>Ithaca: Cornell University Library, arXiv.org</publisher><subject>Compilers ; Debugging ; Java ; Performance enhancement ; Programming languages</subject><ispartof>arXiv.org, 2018-04</ispartof><rights>2018. This work is published under http://arxiv.org/licenses/nonexclusive-distrib/1.0/ (the “License”). Notwithstanding the ProQuest Terms and Conditions, you may use this content in accordance with the terms of the License.</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>776,780</link.rule.ids></links><search><creatorcontrib>Baxter, Samuel</creatorcontrib><creatorcontrib>Nigam, Rachit</creatorcontrib><creatorcontrib>Joe Gibbs Politz</creatorcontrib><creatorcontrib>Krishnamurthi, Shriram</creatorcontrib><creatorcontrib>Guha, Arjun</creatorcontrib><title>Putting in All the Stops: Execution Control for JavaScript</title><title>arXiv.org</title><description>Scores of compilers produce JavaScript, enabling programmers to use many languages on the Web, reuse existing code, and even use Web IDEs. Unfortunately, most compilers inherit the browser's compromised execution model, so long-running programs freeze the browser tab, infinite loops crash IDEs, and so on. The few compilers that avoid these problems suffer poor performance and are difficult to engineer. This paper presents Stopify, a source-to-source compiler that extends JavaScript with debugging abstractions and blocking operations, and easily integrates with existing compilers. We apply Stopify to 10 programming languages and develop a Web IDE that supports stopping, single-stepping, breakpointing, and long-running computations. For nine languages, Stopify requires no or trivial compiler changes. For eight, our IDE is the first that provides these features. Two of our subject languages have compilers with similar features. Stopify's performance is competitive with these compilers and it makes them dramatically simpler. Stopify's abstractions rely on first-class continuations, which it provides by compiling JavaScript to JavaScript. We also identify sub-languages of JavaScript that compilers implicitly use, and exploit these to improve performance. Finally, Stopify needs to repeatedly interrupt and resume program execution. We use a sampling-based technique to estimate program speed that outperforms other systems.</description><subject>Compilers</subject><subject>Debugging</subject><subject>Java</subject><subject>Performance enhancement</subject><subject>Programming languages</subject><issn>2331-8422</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2018</creationdate><recordtype>article</recordtype><sourceid>BENPR</sourceid><recordid>eNqNjUEKwjAQAIMgWLR_WPBciBtrpTcpFfEk1HspJdWUkK3JRny-PfgAT3OYgVmIBJXaZcc94kqkIYxSSjwUmOcqEeUtMhv3AOPgZC3wU0PDNIUS6o_uIxtyUJFjTxYG8nDt3l3TezPxRiyHzgad_rgW23N9ry7Z5OkVdeB2pOjdrFqUBc5XVUj1X_UFeMk2Kw</recordid><startdate>20180416</startdate><enddate>20180416</enddate><creator>Baxter, Samuel</creator><creator>Nigam, Rachit</creator><creator>Joe Gibbs Politz</creator><creator>Krishnamurthi, Shriram</creator><creator>Guha, Arjun</creator><general>Cornell University Library, arXiv.org</general><scope>8FE</scope><scope>8FG</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>HCIFZ</scope><scope>L6V</scope><scope>M7S</scope><scope>PIMPY</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PTHSS</scope></search><sort><creationdate>20180416</creationdate><title>Putting in All the Stops: Execution Control for JavaScript</title><author>Baxter, Samuel ; Nigam, Rachit ; Joe Gibbs Politz ; Krishnamurthi, Shriram ; Guha, Arjun</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-proquest_journals_20720003703</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2018</creationdate><topic>Compilers</topic><topic>Debugging</topic><topic>Java</topic><topic>Performance enhancement</topic><topic>Programming languages</topic><toplevel>online_resources</toplevel><creatorcontrib>Baxter, Samuel</creatorcontrib><creatorcontrib>Nigam, Rachit</creatorcontrib><creatorcontrib>Joe Gibbs Politz</creatorcontrib><creatorcontrib>Krishnamurthi, Shriram</creatorcontrib><creatorcontrib>Guha, Arjun</creatorcontrib><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>Materials Science &amp; Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Technology Collection (ProQuest)</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Engineering Collection</collection><collection>Engineering Database</collection><collection>Publicly Available Content Database</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>Engineering Collection</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Baxter, Samuel</au><au>Nigam, Rachit</au><au>Joe Gibbs Politz</au><au>Krishnamurthi, Shriram</au><au>Guha, Arjun</au><format>book</format><genre>document</genre><ristype>GEN</ristype><atitle>Putting in All the Stops: Execution Control for JavaScript</atitle><jtitle>arXiv.org</jtitle><date>2018-04-16</date><risdate>2018</risdate><eissn>2331-8422</eissn><abstract>Scores of compilers produce JavaScript, enabling programmers to use many languages on the Web, reuse existing code, and even use Web IDEs. Unfortunately, most compilers inherit the browser's compromised execution model, so long-running programs freeze the browser tab, infinite loops crash IDEs, and so on. The few compilers that avoid these problems suffer poor performance and are difficult to engineer. This paper presents Stopify, a source-to-source compiler that extends JavaScript with debugging abstractions and blocking operations, and easily integrates with existing compilers. We apply Stopify to 10 programming languages and develop a Web IDE that supports stopping, single-stepping, breakpointing, and long-running computations. For nine languages, Stopify requires no or trivial compiler changes. For eight, our IDE is the first that provides these features. Two of our subject languages have compilers with similar features. Stopify's performance is competitive with these compilers and it makes them dramatically simpler. Stopify's abstractions rely on first-class continuations, which it provides by compiling JavaScript to JavaScript. We also identify sub-languages of JavaScript that compilers implicitly use, and exploit these to improve performance. Finally, Stopify needs to repeatedly interrupt and resume program execution. We use a sampling-based technique to estimate program speed that outperforms other systems.</abstract><cop>Ithaca</cop><pub>Cornell University Library, arXiv.org</pub><oa>free_for_read</oa></addata></record>
fulltext fulltext
identifier EISSN: 2331-8422
ispartof arXiv.org, 2018-04
issn 2331-8422
language eng
recordid cdi_proquest_journals_2072000370
source Free E- Journals
subjects Compilers
Debugging
Java
Performance enhancement
Programming languages
title Putting in All the Stops: Execution Control for JavaScript
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-07T22%3A58%3A27IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=document&rft.atitle=Putting%20in%20All%20the%20Stops:%20Execution%20Control%20for%20JavaScript&rft.jtitle=arXiv.org&rft.au=Baxter,%20Samuel&rft.date=2018-04-16&rft.eissn=2331-8422&rft_id=info:doi/&rft_dat=%3Cproquest%3E2072000370%3C/proquest%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=2072000370&rft_id=info:pmid/&rfr_iscdi=true