claim

active

claim:studying-programming-systems-requires-a-paradigm-shift-from-programming-languages-where-interaction-between-programmer-and-system-becomes-central-rather-than-program-code-alone

Studying programming systems requires a paradigm shift from programming languages, where interaction between programmer and system becomes central rather than program code alone.

Core assertion that systems perspective is incommensurable with language perspective; interaction, not code, is what matters in systems analysis.

Source paper

extracted_from

Technical Dimensions of Programming Systems

(2023) · Jakubovic, Joel · Edwards, Jonathan · Petricek, Tomas

Neighborhood — ranked by edge-count

Thinkers (1)

thinker

Richard Gabriel
cites
Noted the paradigm shift from study of 'systems' to 'languages' in computer science; informs the distinction between programming languages and programming systems.

Communities (3)

community

Design principles for care-centered systems
members_of
Cross-scale frameworks linking spatial patterns, diagrams, and simplicity as expressions of care in design.
Linda and coordination-oriented programming systems
members_of
Tuple space coordination languages (Linda, Parlog) enabling scalable parallel systems with composable specifications, circa 1980s–90s multicomputer platforms.
Programming systems research framework
members_of
Argues for interaction-centered vocabulary to enable cumulative progress beyond PL theory

Claims (1)

claim

Programming systems research lacks a common vocabulary and systematic framework comparable to programming language research, hindering cumulative progress.
supports
Problem statement motivating the technical dimensions framework; notes that publications tend to present singleton systems rather than addressing issues across multiple languages.

Related by similarity (8)

cosine ≥ 0.65 · no typed edge

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

Paradigm shift from languages to systemsclaim0.817
It has long been said that programming languages need more of the features of natural language, but it has not been clear what the desirable features are.claim0.797
Introduction, motivating the proposal.
A programming language is low level when its programs require attention to the irrelevant.concept0.792
Epigraph by Alan Perlis motivating the search for abstract conceptual models in Fruit's design philosophy.
What are the appropriate boundaries for analyzing a programming system?question0.787
Raised via Java/Eclipse example; boundaries significantly affect analysis and are a design choice (minimal vs. realistic systems).
Programming Systemconcept0.781
Defined as an integrated and complete set of tools sufficient for creating, modifying, and executing programs, including notations, facilities, and interfaces—broader than programming languages alone.
"The runtime architecture of a system" crystallizes the notion that temporal relationships matter more than static code structure.concept0.776
Dynamic programming languages seem to spend much of their time looking up behaviour associatively.claim0.771
An observation motivating the associative model as a unifying primitive.
When a problem has a simple solution, a useful system will give programmers access to the simple solution; Parlog forces complex solutions to simple problems.claim0.763
Critique that Parlog's abstraction level is too high and restrictive.

Cross-corpus bridges (1)

same_concept_as · Nomic cosine

External markdown files that talk about the same concept as this entity.

alexander
The Art, Science, and Engineering of Programmingpapers/extracted/2022-04-30_Stefan-Lesser_prog22-master.pdf_978acd.md0.819