Live coding languages are classified by target medium, host platform, and implementation language

There is no single live-coding language: the ecosystem holds dozens of distinct languages and environments. A useful way to navigate them is by three axes the awesome-livecoding index tags every entry with. Target medium: audio, visuals, or both (audio-visual). Host platform: browser (zero-install web apps) versus desktop (Windows/macOS/GNU-Linux installs). Implementation/host language and paradigm: Haskell, Python, JavaScript, Ruby, Rust, Lisp, or a visual/graphical patching language. A further practical axis is licence (most are FLOSS; a few are commercial or freeware) and maintenance status (some entries are flagged inactive). Reading these tags lets a newcomer pick a tool that fits their platform and goal rather than assuming live coding means one specific environment.

Examples

Browser + audio+visuals: Gibber (web JavaScript FLOSS audio visuals). Desktop + audio: TidalCycles (Haskell, SuperCollider). Browser + visuals only: Hydra. Visual patching: Pure Data, Max.

Assessment

Given the tag line for a language (e.g. web JavaScript FLOSS audio), state its target medium, host platform, and licence. Then name one browser-only and one desktop-only live coding language.