| ▲ | raincole 8 hours ago | |
It seems that any data-orient approach would inevitably evolve into a programming language given enough time. One day we might even see for-loop in CSS... | ||
| ▲ | jerf 8 hours ago | parent | next [-] | |
I have a theory that in such cases one might as well just give up and write a Turing-complete language in the first place, as the sort of TC-complete languages we get with this sort of "slowly but surely backed against the wall" situations are way worse than just starting from scratch. I hypothesize a TC-complete language for something like CSS that included deep tracking under the hood for where values are coming from and where they are going would be very useful, i.e., you would have the ability to point at a particular part of the final output and the language runtime could give you a complete accounting of where it came from and what went into making the decisions, could end up giving us the auditability that we really want from the "declarative" languages while giving us the full power of the programming langauges we clearly want. However I don't have the time to try to manifest such a thing myself, and I don't know of any existing language that does what I'm thinking of. Some of the more powerful languages could theoretically do it as a library. It's not entirely unlike the auditing monad I mention towards the end of https://www.jerf.org/iri/post/2958/ . It's not something I'd expect a general-purpose language to do by default since it would have bad general-purpose performance, but I think for specialized cases of a TC-complete configuration langauge it could have value, and one could always run it as an debugging option and have an optimized code path that didn't track the sources of everything. | ||
| ▲ | andreareina 8 hours ago | parent | prev | next [-] | |
There are languages specifically for writing configs. Like dhall https://dhall-lang.org/ | ||
| ▲ | eblume 8 hours ago | parent | prev [-] | |
That's my thought as well. I predict we'll be seeing SDK's for generating github workflows by mid-2026. Maybe pulumi will get an extension for it. (I'm well aware that codegen yaml has been a thing for a long time, but I'm thinking about something targeting github workflows _specifically_.) TBH it's getting a bit exhausting watching us go through this hamster wheel again and again and again. | ||