40 Followers
102 Following
1.1K Posts
Cajun Commie. Nerd. Swamp socialist. Engineer. Programmer. Dad. Linux, BSD and all open systems stuff enthusiast. Music fan.
pgp01EF9314E5638E1E44FCEF559CBD4CF409E7C52B
Open Source's Second Death

Ernest Hemingway said that every man has two deaths, when he is buried in the ground and the last time someone says his name.

Jesse’s Substack
C-a k y
Will the firmware be upgraded, by and by Lord, by and by. There's a better version waiting, in the sky Lord in the sky.

Listen to track in TIDAL - J A Y E L E C T R O N I C A: A.P.I.D.T.A.

https://tidal.com/track/134189411

@abathur yeah, basically. I was not being super technical, but that's what I meant, except the middle: It's just a file. It can be instructions or it can be the content itself.
Leaving Haskell behind

For almost a complete decade—starting with discovering Haskell in about 2009 and right up until switching to a job where I used primarily...

Infinite Negative Utility
I should re-read the Nix paper again. I’m sure it covers some of this. But, seems like you could have “files” that are links to instructions for building from which you can link to built artifacts, as long as they match. Then make some choices over when to use “cached” ones v. built ones. Yeah, I guess guix and nix do a lot of this. I need to explore them more.
@jk we should do GNP9: GNP9 is Not Plan 9, & it’s just a user-space running overlay with what the desktop cares about & then each program can request/inherit their own views
@jk the wild thing about this, too, is that some of the tools like docker and venv sort of break the "systems view" here because there could be stuff running using filesystems that you don't see from the "default" view :/ Hm. There probably is a way to see the cgroup fs mounted namespaces as a filetree in linux, at least, but I don't think it's in the sysadmin's "default view" so to speak. Your idea of different filesystem trees for different users/tasks is very plan9 and very UNIX, though, imho.
@jk Like imagine the simplicity, "build a tree of stuff and set your root there." You can do that without docker or venvs, really. And, shoot, you could probably build Python and everything in that "root." Don't even worry about venvs; use that local Python install in your root, etc etc