IME videos + examples (repo of various configs for many common and less common scenarios) are much more effective (if up to date) than classic guides, specially for on-screen usages, while books are far more effective for the printed world.
Producing books demand a significant effort, especially if it's a teaching book, not a mere reference and still cover enough, keeping it up to date in a modern project it's almost a nightmare, so videos and examples remain the quickest and easiest solution.
Personally the main issue I have with NixOS is:
- the Nix language, especially compared to Guix System
- the lack of quickly digestible AND still deep enough docs
I've using NixOS as my main desktop and homeserver since some years and I still have to know Nix enough to be really "confident enough"...
Wikis by their very nature allow for people to catch these problems and let people know where there's shortcomings.
As anybody can just hit record on a video and log the entire thing, having a reference video for a process is easy enough, as is turning a video into a transcript automatically that can then be embellished upon. Screenshots can also be taken from videos if there's something visual that may be lost in text.
Yes, videos are not good for accessibility, and a lot of people in software don't get on with videos. Same goes for people whose first language is not English.
Producing books demand a significant effort, especially if it's a teaching book, not a mere reference and still cover enough, keeping it up to date in a modern project it's almost a nightmare, so videos and examples remain the quickest and easiest solution.
Personally the main issue I have with NixOS is:
- the Nix language, especially compared to Guix System
- the lack of quickly digestible AND still deep enough docs
I've using NixOS as my main desktop and homeserver since some years and I still have to know Nix enough to be really "confident enough"...