English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Context. Software development pipelines are used for automating essentialparts of software engineering processes, such as build automation andcontinuous integration testing. In particular, interactive pipelines, whichprocess events in a live environment such as an IDE, require timely results forlow-latency feedback, and persistence to retain low-latency feedback betweenrestarts.  Inquiry. Developing an incrementalized and persistent version of a pipelineis one way to reduce feedback latency, but requires dependency tracking, cacheinvalidation, and other complicated techniques. Therefore, interactivitycomplicates pipeline development if timeliness and persistence becomeresponsibilities of the pipeline programmer, rather than being supported by theunderlying system.  Approach. We develop Pipelines for Interactive Environments (PIE), aDomain-Specific Language (DSL), API, and runtime for developing interactivesoftware development pipelines, where ease of development is a focus.  Knowledge. PIE provides a straightforward programming model that enablesdirect and concise expression of pipelines without boilerplate, reducing thedevelopment and maintenance effort of pipelines. Compiled pipeline programs canbe embedded into interactive environments such as code editors and IDEs,enabling timely feedback at a low cost.  Grounding. Compared to the state of the art, PIE reduces the code required toexpress an interactive pipeline by a factor of 6 in a case study onsyntax-aware editors. Furthermore, we evaluate PIE in two case studies ofcomplex interactive software development scenarios, demonstrating that PIE canhandle complex interactive pipelines in a straightforward and concise way.

PIE: A Domain-Specific Language for Interactive Software Development Pipelines