@this_xor_that just reading your alpaca paper. So interesting! The approach of linking configuration to output is very similar to what I've been doing – I just turned my configuration file format into a functional language 😀
Top-level
@this_xor_that just reading your alpaca paper. So interesting! The approach of linking configuration to output is very similar to what I've been doing – I just turned my configuration file format into a functional language 😀 6 comments
@jonathanhogg oooh this and the docs are great. Thanks for sharing! It seems like a nice example of having a language keep a structured hierarchy too. @this_xor_that the hierarchical aspect was super-important to me in designing Flitter. I spend a lot of my time tabbing in blocks and adding a parent as I develop an idea. E.g., “these things, but randomly rotated and translated”, “that, but now 100 of them”… @jonathanhogg oooh. I do the same of inserting hierarchies, but my set up means I usually have to update the rust code, so it’s not livecoded. |
@jonathanhogg oh that's super cool! do you have a code sample I could peek at by chance?
the yaml+expr setup was a little out of necessity and is janky at times, but I also like some aspects of it (the file whitespace has to match the structure of the input configuration, so it never gets tooo messy.)