Architecture decisions
Why nada is built the way it is: each significant decision as a short record (context, the decision, its consequences), in the ADR format. A decision is never edited away: a later one supersedes it. Sources: docs/adr.
Record architecture decisions
Decisions about how nada is built (its dependencies, its boundaries, the trade-offs it accepts) were made in conversations and commit messages, where nobody finds them later. A con…
MPD is the engine; nāda is the interface
A music player needs gapless playback, a library index, a queue that survives restarts, and audio output handling. MPD has done this for twenty years, and Vayu already ran it.
YouTube songs are stream URLs in MPD's queue
rmpc downloaded YouTube songs before playing them: a delay before every song, and files piling up. But YouTube's stream links expire after a few hours.
Line up what plays next, like YouTube
Picking every next song by hand breaks listening. YouTube's mixes are good at what comes next.
A download replaces the stream in place
Saving a song you're listening to shouldn't interrupt it, and the queue shouldn't end up with both copies.
Vim keys with modes, counts and registers
The people nāda is for edit text with vim. A player with its own key scheme is another thing to learn.