The UNIX system has been in wide use for over 20 years, and has helped to define many areas of computing.
Post
The mechanism is entirely transparent, so that existing software can be executed either locally or remotely, with no change to that software.
P A N T S
A A
N N
T T
S S
The decision about where the new process is to execute is specified by information associated with the calling process.
trying to reach through the screen again because i finally found someone who cares
"structured advice list" all they need to say is dependency graph now
see here's the thing they knew they were building a goddamn operating system and that's one thing i didn't realize at the time
but their unix is obviously just my bazel
yeah so they did absolutely do better than me 40 years earlier and that's on me to catch up
The semantics of the available functions by which processes interact determines, to a large extent, the difficulty involved in supporting a transparent process facility.
posix reading my email screaming crying throwing up
The most difficult part of these functions' semantics is their expectation of shared memory.
TRUTHNUKE!!!!!!!
Virtually all processes read and write substantial amounts of data per system call.
so funny story
As a result, most collections of Unix processes designed to execute on a single machine run very well when distributed on LOCUS.
this with pants and bazel except bazel literally only works in the "cloud". and the pants capacity for recursive/monadic tasks (dynamic dependency generation e.g. resolving a lockfile) is specifically how we could do outline compiles with twitter rsc locally and then farm scalac out to finish the job. so you control it locally and get results locally, and the cloud is used as extra capacity instead of controlling your organizational capacity
so google really didn't like that
literally these corps are nothing when we dream together. that was 2019 when google killed rust and pants because we showed them up and demonstrated their attempts to RCE every internet user with chrome and every software user with bazel were perhaps not such noble schemes to protect users against evil!
perhaps it's strange that the surveillance company who graciously negotiates TLS certificates for you keeps describing network code as tricky and unsafe! perhaps when they graciously offer a DRM ✅ that requires you to leave your python packages alone in a room with their server before publishing to pypi that........you are not keeping your users safe with the ✅!
(the astral engineer who slanders zip files wrote the microsoft DRM and removed pgp keys from pypi.)
astral got funding from google and chainguard and themselves contributed funds to one of the literally 3 separate rust2c "forks" of zstd. chainguard is the startup who developed the DRM ✅ technology
unfortunately, one of chainguard's cryptographers (santiago) is pretty cool. i should reach out to him because his work on attestation graphs is also how you'd do signed builds if you wanted to use your own hardware
which of course means process isolation guarantees..........and i happen to know an agender who's into that freaky shit
@hipsterelectron i play with VM APIs, but “gender”.