question
active
question:lack-of-common-vocabulary-for-programming-systemsLack of common vocabulary for programming systems
Source paper
extracted_from(2023) · Jakubovic, Joel · Edwards, Jonathan · Petricek, Tomas
Related by similarity (8)
cosine ≥ 0.65 · no typed edgeEntities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.
- Problem statement motivating the technical dimensions framework; notes that publications tend to present singleton systems rather than addressing issues across multiple languages.
- 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.
- What unexplored or overlooked possibilities exist in the design space of programming systems?question0.770Motivating question for using technical dimensions as a map to reveal gaps in the design space.
- A programming language is low level when its programs require attention to the irrelevant.concept0.753Epigraph by Alan Perlis motivating the search for abstract conceptual models in Fruit's design philosophy.
- Core assertion that systems perspective is incommensurable with language perspective; interaction, not code, is what matters in systems analysis.
- Raised via Java/Eclipse example; boundaries significantly affect analysis and are a design choice (minimal vs. realistic systems).
- Parlog's merge process for client-server is unnecessarily complex; Linda's tuple operations remain flexible across problem variants.