emily-modifiers VS stenophone

There are no easy/standard steno chords for typing keyboard shortcuts (e.g. Ctrl+S to save file). (I like to use [Emily's Modifier Dictionary](https://github.com/EPLHREU/emily-modifiers) for this.)

You can easily extend Emily Symbols to do whatever symbols you like. You can also use Emily Modifiers to take advantage of any keyboard shortcuts that exist in the editor you are using.

Have a gander at this theory component dictionary for modifiers as an example of what's possible.

Personally I've never been attracted to writing SuperCollider code, especially not in a live context, largely due to its syntax, but also its complexity.

So-called 'visual programming languages' I don't find interesting for performance, since they rely on the mouse for program manipulation.

For me Tidal's mini-notation is the greatest music sequencing tool of all time, bar none. Every time someone shows me a sequencer I can usually write the Tidal code in my head on the spot, and save $1000s on redundant hardware. It could only be beaten by being turned into a physical instrument, something I've tried to do in the past: https://github.com/jarmitage/Stenophone.

That being said, even though I'm evidently a big Tidal fan I would still call attention to ICLC and HLCI, where amazingly creative and interesting new systems and approaches are being proposed every year:

https://iclc.toplap.org/

https://hybrid-livecode.pubpub.org/

Mirabai Knight's talk about this is one of my all time faves: https://www.youtube.com/watch?v=Wpv-Qb-dB6g

Inspired me to try to create a live coding musical instrument based on it: https://github.com/jarmitage/stenophone / https://iclc.toplap.org/2017/cameraReady/stenophone_camready...