koto

Koto shares the same string representation as Rust, Koto lists are just wrapped `Vec`s, etc).

If he plucked one of the 13 strings of a koto, we wouldn't say he is just remixing the vibration of the koto.

But let's say, want to keep the option open to participate in Rust-based projects which support Koto et al.?

You should take a look at Koto Programming Language, I’ve been trying to keep an eye on it.

We can imagine a harp like instrument (or koto) with multiple steel strings, oscillating under a Sustainiac-like pickup feeedback system, and used as the basis for synthesis.

Sorry, I meant the Koto language and built-in library compatibility story.

Would you say Koto (or some direct competitors, for that matter), is viable to learn when I otherwise don't intend to learn Rust at all?

Frets are already on equal temperament on the vast majority of mainstream guitars; you're not getting away from equal temperament unless all you play is open strings, like a koto/harp.

What I've had in mind with Koto is that when I need strictness and precision I'll generally be using Rust, and Koto is more intended for another aspect of programming where I want things to be much more fluid and easy-going.

In my tests it's been ~1.5-2x faster than Rhai, but Koto's still some way behind Lua in benchmarks so I'm not trying to make a big claim here (although that said one of the reasons I started work on Koto was to avoid the runtime overhead of Lua <-> Rust conversions, e.g.

Rust doesn't have a stable ABI so to make sure that dynamically loaded Rust packages are compatible, either Koto would need to be in the business of Rust toolchain management so that packages can be recompiled when needed, or an API layer would be needed.

I'm tempted by koto because it already has something like `|` operator (`->`) and isn't just "Rust, but embeddable" (Rust is an implementation detail; it shouldn't bleed through).

When you take out “I am Nash” you are left with “sato” and “koto” Japenese is the key because if you didn’t know the language then you could never match the words to verify the code cracking.

Koto looks more like FP an stream processing, with pervasive anonymous functions, very simple data structures, and an emphasis on iterators.

Haha well I'm sure if you put your mind to it you could create some madness in Koto!

Koto creator here, nice surprise to see this on HN so I'm a bit late to the discussion.