I spent some time this week re-implementing a step sequencer inside of gibber, the live coding environment I work on. You can now either use

x / X

to indicate trigger / accented trigger or enter velocities using hexadecimal. Patterns can be manipulated globally or an a per pattern basis. https://twitter.com/gibber_cc/status/1334200044342243328

it’s remarkable how quick and comprehensible gibber is

Which language syntax is that, and how does your "intellisense" system work?

@David Piepgrass in that particular example, it’s vanilla (albeit idiosyncratic) JavaScript… but there is also an extra parser in the environment to handle operator overloading when defining signals. I have a toolchain that takes JSON metadata for objects / functions and outputs Markdown documentation, feeds the autocomplete (Codemirror + Tern), and provides expected bounds / sample rates / curves to enable reactive programming across different types of a/v/interactive signals.