faust

rgy-saving modes, math accelerators (Cordic for sines/cosines), audio peripherals > STM32L4 Series | ARM Cortex-M4F | ~100 µA / MHz | mature, ultra-low-power, robust I2S audio support, sleep state grame-cncm/faust: Functional programming language for signal processing and sound synthesis / [that compiles to microcontroller DSP code, LLVM IR,] https://github.com/grame-cncm/faust Then a Rust-based OS for microcontrollers; to isolate devices and device drivers from other processes; I'd like to learn this too (so this is worth researching) Rust packages for DSP: embedded-hal, embedded-io, rand_core Navigating the Embedded Rust Ecosystem https://www.theembeddedrustacean.com/p/navigating-the-embedd... https://google.github.io/comprehensive-rust/bare-metal/micro... hubris > Flash instructions already mention an STM32 F but not yet U or L: https://github.com/oxidecomputer/hubris#flash Task: Add support for STM32U and STM32L to hubris "Navigating the Embedded Rust Ecosystem" https://www.theembeddedrustacean.com/p/navigating-the-embedd... The micro:bit has a speaker and something like a DSP and rust support, though it's not going to run JUCE and BespokeSynth ; kk Just rtic, cortex-m-rt, and nrf52833-hal (for micro:bit v2) might be sufficient but there's already microbit_bsp: microbit_bsp is a board support package (BSP) library for the micro:bit v2 and newer: https://docs.rs/microbit-bsp/latest/microbit_bsp/ Another task; Develop and test a board support package for low-power chips for hosting effects from JUCE compiled with or like Faust. But then contain agent sessions; e.g. Hubris has no shared memory so audio streams must be shoveled over message passing -- Back to agent sandboxing; It looks like WebKitGTK uses bubblewrap on linux unless running in a flatpak, because flatpaks don't have permission to create namespaces so bwrap can't run. Bubblewraplauncher.cpp: https://github.com/WebKit/WebKit/blob/main/Source/WebKit/UIP... FlatpakLauncher.cpp: https://github.com/WebKit/WebKit/blob/main/Source/WebKit/UIP... CF workers support nested agent isolates since 2026-03: https://blog.cloudflare.com/dynamic-workers/ dloss/awesome-agent-sandboxes: A curated list of sandboxing solutions for AI agents https://github.com/dloss/awesome-agent-sandboxes

t, sometimes implement something as best you can and then describe what you've got. Implementation language will affect how long it takes to get something working, how good the thing will be and what you'll think about along the way. The usual guidance is to write in something familiar to you, ideally with pattern matching as compilers do a lot of DAG transforms. - I'd say that writing a language in C took me ages and forced me to really carefully think through the data representation. - Writing one in lua took very little time but the implementation was shaky, probably because it let me handwave a lot of the details. - Writing a language in itself, from a baseline of not really having anything working, makes for very confusing debugging and (eventually) a totally clear understanding of the language semantics. Good luck with the project.