dyon VS interfaces

Reminds me of Dyon, a scripting language for Piston.

It's dynamically typed and uses lifetimes instead of a garbage collector.

https://github.com/PistonDevelopers/dyon/issues/173

Piston + Dyon is a nice combo. If I need something simple, then I use Dyon-Interactive.

Another way to learn is by using Dyon, which has a lifetime checker, but no borrow checker. In Dyon, you only need to put mut in front of arguments, so it is a little more ergonomic than in Rust, but you'll love the extra safety in Rust when maintaining libraries.

This should be a good use-case for rust-based scripting languages, I think.

I loosely followed a project of that kind a while ago, I don't quite remember if it was Gluon [0] or Dyon [1]. Not sure if these are still active, or if another competitor showed up in meantime.

___

[0] https://github.com/gluon-lang/gluon

[1] https://github.com/PistonDevelopers/dyon

Dyon

These are the scripting languages i saw recently gluon, gleam, dyon, rune, mun. I like mun most because it resembles rust most. There is also this and this thread.

Dyon is a pretty cool Rust-like scripting language.

I like how wasmCloud does things - they define the interface using smithy like this https://github.com/wasmCloud/interfaces/blob/main/httpserver/httpserver.smithy (in the httpserver interface, the wasm side receives http requests as structs, and replies with responses as structs. The native-code side is responsible for listening on the TCP port etc. There are a bunch of other first-party interfaces, including an httpclient interface, for outgoing requests initiated by wasm). They then generate basic interface code for all supported languages from the smithy definitions. They also hand-write some helper functions, to make things easier on the wasm side (this isn't the same from language to language - there are more helpers for rust than other languages).