Nice to Have: Think about exposing Satin API to Lua or some other scripting engine

[vade]

Today, Velvet, our experimental live coding prototype does a bunch of crazy shit to make Swift do stuff it really doesnt want to do.

In my estimation, using Swift is the wrong language for a live coding setup for Satin, as

• Swift allows you to do literally fucking anything
• Swift requires Velvet to know that you want to do fucking anything, and that to compile that anything it can link
• Velvet is not meant to be a full IDE, but rather a Satin playground.

I think if we can 'scope' some bindings and expose them to an embedded runtime, the 'safety' of Velvet would be better.

The first step to that is picking a language and thinking about bindings.

[aleith]

Have you considered Zig language? it's optimised for "data design" level programming ie speed, low level types, graphics etc and has the bonus of being able to compile source code cross platform (macOS, windows and linux, which i know is outside scope of Satin/Fabric).

there's also a scripting language derivative called Cypher (IIRC) which is still very much in beta but it's based on Zig and a blitzing fast for an interpreted (JIT compiled) scripting language in comparison with python, optimised JS/typescript etc.