2 ms·
I suspect it will not be a language in the traditional sense. Instead of describing how to build a system, it would describe the system's entities, relationship
by shadowAuror 2mo ago
I suspect it will not be a language in the traditional sense. Instead of describing how to build a system, it would describe the system's entities, relationships, goals, constraints, NFRs etc...
The application model becomes the source of truth, and the code will be the generated artifact. A single spec defined and code generated will be optimized for web, mobile, desktop, api, etc...
The spec itself can be in a yaml type format or a hierarchical knowledge graph...
- huurtehoog 2mo agoThis reads exactly like 'model driven development' and 'language workbenches' hype from 20 years ago. Uncanny. Jet Brains has had that on early access since 2005. Literally 20 years ago people were dreaming about this new abstraction thing. Text source code is a low energy configuration for representing software. Using LLMs is a much higher energy state.
- shadowAuror 2mo agodidn't know about these... I need to go read up on them now...
- senorqa 2mo agoInteresting. I've never heard of this before https://en.wikipedia.org/wiki/Language_workbench https://en.wikipedia.org/wiki/Language_workbench