Ignas Kiela (ignaloidas@not.acu.lt)'s status on Wednesday, 19-Jul-2023 02:57:09 JST

@lanodan@queer.hacktivis.me tbh I don't particularly care about repo adoption, if I went ahead far enough with the language, I'd also go for my own kernel and stuff

Somewhat automated patching would be possible as long as the API's don't matter (a matter of changing name-hash mapping and updating it all the way up, would be tools for that because it both wouldn't be stored as traditional files (way more annoying to do content addressing on things inside of files than the files, having a "source database" seems nicer). And FWIW some stuff for vuln patching could be nicer, e.g. in a security report you'd get the hashes of the functions that are vulnerable, and you just scan through all packages of the language to check if the specific function is used, so you can be a lot more granular on what to spend CI time on while updating.

But no, there will be absolutely NO way to include "system" libraries, everything would have to be in the source library, and in the source library only, no going out to internet to fetch stuff (separate tools to do that and put it into the source library).