Post B4pAOU4TiOqWQEHoTQ by neauoire@merveilles.town
 (DIR) More posts by neauoire@merveilles.town
 (DIR) Post #B4pAIPfJBRIf1HcP2W by chrisamaphone@hci.social
       0 likes, 1 repeats
       
       re: https://hci.social/@chrisamaphone/116325060049701188taking off my "impartial observer" hat for a moment (and so breaking out of the thread), one opinion i've started solidifying is that we need stable (or one might say "archival") proof languages, alongside those that actively evolve. a big motivation for me is to develop teaching materials that still run in a decade (Explaining), but i think there are good Convincing-aligned reasons to want this as well.RT: https://hci.social/users/chrisamaphone/statuses/116325060049701188
       
 (DIR) Post #B4pAOU4TiOqWQEHoTQ by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @chrisamaphone reading the preprint at the moment, this is a VERY interesting overlap of interests for me! Well done you and your team for thinking about these ideas, I honestly didn't expect to be seeing stuff like this in my lifetime.
       
 (DIR) Post #B4pB5Z2N7xDsHAqLWC by chrisamaphone@hci.social
       0 likes, 0 repeats
       
       @neauoire thanks! i'm interested in hearing what you think if you have a chance to read further on
       
 (DIR) Post #B4pB5ZJO6gpl7wnw2a by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @chrisamaphone I have thoughts, but I wanna read through first :)
       
 (DIR) Post #B4pCT3ymLr6sr6vpNg by chrisamaphone@hci.social
       0 likes, 0 repeats
       
       arguably we should also want archival programming languages more generally. sometimes, a language whose features cease to evolve is called "dead". but perhaps we should reserve "dead" for languages whose programs no longer run, and use "archival" for those whose implementations are maintained while their feature sets remain stable (thx @simrob for planting this lexical seed in my head)
       
 (DIR) Post #B4pCT4EjOXs1eaOZFI by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @chrisamaphone Have you ever come across Kragen's notes on using UVMs for archival? This might be a good entry into the topic and probably has some usable ideas for your work:https://dercuano.github.io/topics/archival.html