About ProWeb

Full-fledged web applications have become ubiquitous on desktop and mobile devices alike. Whereas “responsive” web applications already offered a more desktop-like experience, there is an increasing demand for “rich” web applications (RIAs) that offer collaborative and even off-line functionality —Google docs being the prototypical example. Long gone are the days when web servers merely had to answer incoming HTTP requests with a block of static HTML. Today’s servers react to a continuous stream of events coming from JavaScript applications that have been pushed to clients. As a result, application logic and data is increasingly distributed. Traditional dichotomies such as “client vs. server” and “offline vs. online” are fading.

The ProWeb21 workshop is a forum for researchers and practitioners to share and discuss new technology for programming these and future evolutions of the web. We welcome submissions introducing programming technology (i.e., frameworks, libraries, programming languages, program analyses, and development tools) and formalisms for implementing web applications and for maintaining their quality, as well as experience reports about their usage.

2020 Talks

Since last year’s edition (ProWeb20) was cancelled due to the pandemic, we are delighted to host the following ProWeb20 talks at ProWeb21:

• Evolution of the WebDSL Runtime (Danny Groenewegen, Elmer van Chastelet, and Eelco Visser)
• Tamper-proof security mechanism against liar objects in JavaScript applications (Angel Luis Scull Pupo, Jens Nicolay, and Elisa Gonzalez Boix)

Accepted Papers

Call for Contributions

The ProWeb21 workshop is a forum for researchers and practitioners to share and discuss new technology for programming these and future evolutions of the web. We welcome submissions introducing programming technology (i.e., frameworks, libraries, programming languages, program analyses, and development tools) and formalisms for implementing web applications and for maintaining their quality, as well as experience reports about their usage. Relevant topics include, but are not limited to:

• Applications of AI to web software development: code models, code prediction, change impact analysis, automated testing
• Web App Quality: static and dynamic program analyses, metrics, development tools, automated testing, contract systems, type systems, migration from legacy architectures, web service APIs, API conformance checking
• Designing for and hosting novel languages on the web: compilation to JavaScript, WebAssembly
• Multi-tier (or tierless) programming: new languages and runtimes, tier-splitting compilers, type systems
• Principles and practice of Web UI programming: data binding, reactive programming, virtual DOM
• Data sharing, replication, and consistency: cloud types, CRDTs, eventual consistency, offline storage, peer-to-peer communication
• Security on the new web: security policies, policy enforcement, membranes, vulnerability detection, dynamic patching
• Surveys and case studies using state-of-the-art web technology (e.g., WebAssembly, WebSockets, Web Storage, Service Workers, WebRTC, Angular.js, React and React Native, TypeScript, Proxies, PureScript, ClojureScript, Amber Smalltalk, Scala.js)
• Ideas on and experience reports about: how to reconcile the need for quality with the need for agility on the web, how to master and combine the myriad of tier-specific technologies required to develop a web application
• Position papers on what the future of the web will look like

This year, we are accepting three types of submission:

• Full papers, position papers, and experience reports: 8-page papers describing novel research, which, when accepted, will be included in the ACM Digital Library.
• Demo papers: 4-page illustrating demonstrations of tools and prototypes.
• Presentation abstracts: 2-page extended abstracts.

Presentation abstracts will not be included in the ACM Digital Library but will be included in an informal pre-proceedings on the website. We very much welcome presentation abstracts about work already published elsewhere, or giving an overview of an existing system, and the format is designed not to preclude future publication.

Submissions should be in ACM SIGPLAN two-column format (see https://www.sigplan.org/Resources/Author/). References are not counted in the page limits.

If you have any questions or wonder whether your submission is in scope, please do not hesitate to contact the PC co-chairs.