mmids VS rune

I've worked a lot on a media workflow server with the intention that it can be used by both open source and non-open source projects (https://kalldrexx.github.io/mmids/). I licensed it as MIT specifically because if some users want to customize it and add proprietary integrations they can do so without being forced to open-source their integrations.

Finally, this is all composed together in the final application. When anyone wants to provide custom functionality, all they have to do is modify their own main.rs file and omit things they dont' want, and add composition for things they now want.

A Lisp, a weird dialect of Lisp, is not better than Lua. Why use Rune [0]?!

[0]: https://rune-rs.github.io/

This is what I based my comment on - https://github.com/rune-rs/rune/issues/444

Late start today as well. I really thought today would be the day that I'd have to abandon my goal of no heap allocations. But, luckily I had an arena allocator available that I could fairly easily adapt to store data on the stack. And with some tweaks we have today's solution:

I'd have given you bonus points for using a rust styled scripting language like rune but that's pretty neat still

As note about using rust syntax for scripting: https://rune-rs.github.io/

I know you said you don’t want to embed another language but IMO Rune is worth a consideration here. It can be a pretty thin abstraction over rust by passing native structs to scripts and calling methods on them. The syntax and semantics are very close to rust so it feels natural. https://github.com/rune-rs/rune

The biggest technical difference I'd say is that Rune uses a stack-based machine which makes adding deep C support somewhat obvious while Rhai performs AST walking to execute scripts.