The conclusion I came to personally goes as thus:
- Can we do better than the current industry standard?
Yes. A lot of jargon is derived from stuff that used to be ubiquitous but now is very rare. In some cases it's fine to keep it around if it's well-understood (💾 for save, "footage" for, well, source material even though it now is measured in gigabytes, rather than feet of film), but for Ripple, that's not the case - especially as signal ripples exist and are undesirable, and in the context of audio in particular it's not unreasonable to assume some people have come across it.
In order to avoid jargon, a good (but perhaps not massively elegant) solution is to just describe what the options do:
- Ripple Cut -> Cut and close gap
- Ripple Delete -> Delete and close gap
- Ripple Paste -> Paste while creating room for the paste
The latter feels way clumsy, so we can try another word for paste which has some connotation with the actual "wedge it in there" action:
This is the option Premiere uses and the one I'd use as well. (That said, Premiere still uses ripple in other contexts.)
- Is avoiding the jargon in this particular case good in the long run?
This probably depends on the target audience more than anything. If you want to target long-time industry professionals who simply are used to these terms and also metaphors that are outdated by 20 years, you're probably putting yourself at a disadvantage to other competitors. However, if you're targeting new users with no prior knowledge, avoiding obscure jargon makes the app much easier to understand.