cli-guidelines VS redox

The Command Line Interface Guidelines [1] says:

> Do not read secrets from environment variables

> Secrets should only be accepted via credential files, pipes, `AF_UNIX` sockets, secret management services, or another IPC mechanism

Which one of these do you use? On github it seems common for projects to use environment variables for secrets.

[1] https://clig.dev/#environment-variables

Seems they took a small step back from their previous "don't bother with man pages" stance. Now it's "Consider providing man pages."

I still find it a rather shocking order of priority, honestly.

https://clig.dev/#documentation

- E. `blah project foo --edit`

Wondering if there was any guidance on this from the UNIX people. Perhaps scoping should be done using the file system. `cd path/to/project && blah edit`. Like git does with `git --cwd=path/to/project`. Maybe a virtual FS could even be used. Then you wouldn't have to continuously type in the scope with each command. Interesting thinking about how to maintain state in the terminal...thinking about how Python's virtual env bin/activate modifies the shell.

Found an interesting guide here: https://clig.dev/

Capturing these guidelines is one of the primary reasons that https://clig.dev/ exists.

You may want to take a look at various existing CLIs to get inspiration on how they operate, the user feedback loop and the ergonomics on using them. Here is a great website on some CLI structing guidance https://clig.dev/

Redox is another full fledged OS written in rust by Pop OS developer

https://github.com/redox-os/redox

Even in the noncommercial world, Hurd's gone precisely nowhere. RedoxOS is a toy and had a GUI within a year or so. Brutal got in within two. SerenityOS not only built a GUI but the beginnings of the first greenfield web browser to gain any semblance of modern standards support in the past several decades. Honestly, what's Hurd doing wrong to flounder so hard?

[0] https://github.com/redox-os/redox/releases/tag/0.0.3

[1] https://github.com/brutal-org/brutal/releases

[2] https://serenityos.org/happy/1st/

Ah yes, std, that famous crate that is unusable for systems programming. God forbid anyone do any "systems" programming that uses std.

Operating System: Theseus, Redox

Looks like C++ to me!

And my point is that when you mention OS-es like Mezzano (3k stars on Github, a dozen contributors [1]) and Redox (13k stars, 80 contributors [2]), but don't mention Serenity (18k stars, over 100 contributors [3] (Github limits this view to the top 100)) it seems funny.

[0] https://github.com/SerenityOS/serenity/tree/master/Kernel/Ar...

[1] https://github.com/froggey/Mezzano/graphs/contributors

[2] https://github.com/redox-os/redox/graphs/contributors

[3] https://github.com/SerenityOS/serenity/graphs/contributors

Side note, blog posts may have been quiet but there's still been some commit activity here and there.

>I wish opportunities had been around when I was learning to program.

And yet now, we have plenty of projects and nobody contributing.

https://github.com/redox-os/redox/graphs/contributors

This graph doesn't look so healthy. Projects with one major contributor tend to die the moment that contributor loses interest.

Which leads me to wonder, if rust is so popular, and this is one of the most relevant rust projects in the wild, why is this essentially a single contributor repo? Linus didn't write Linux by himself. Redox is never going to happen with a single developer.

Doesn't anyone want a memory safe OS and micro kernel? What does this say about the demand for memory safe systems languages?

I think the guy behind RedoxOS works for them.

redox os is rust operating system without c , here

RedoxOS, an OS written in Rust A tutorial on making an OS in Rust, complwte with bootable source