lucet VS specs

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

The bytecode alliance had the lucet project which would be an OS executing WASM application, enabling very strict sandboxing.

References for anyone following: wasmtime Lucet

I guess lucet could be an under-layer for this but it's not really the same, different levels of the stack. Fascinating.

I also want to use this opportunity to say a big thank you to the teams working on Rust, Wasmer, Wasmtime, Lucet and waSCC. It would be impossible to build Lunatic without all the hard work put into this projects.

The question arises from seeing a plethora of projects using ECS: hecs , Bevy , specs, legion

specs

The official 3d rendering client uses a custom engine called Voxygen. They use Specs for logic.

Rust has a delightful ECS library, specs, that I absolutely love. It has safe multi-threaded execution built right in, which is fantastic for the pretty parallelizable work I was doing. Concurrency in C++ is nasty business on the best of days, and I've run into so many nasty bugs with the custom system I've had to build out to fit the web's weird threading model.

Man, this Specs [0] library is so strange to me, coming from a Unity background. Is there some sort of comparison as to why one way is better than the other?

[0] https://specs.amethyst.rs/

Hi everyone - I just picked up one of my long-unfinished side project built with Rust and would like to show it to you here. It's a clone of the famous(?) Winterbells game. It's written entirely in Rust and uses OpenGL and an entity-component-system architecture ([the `specs` crate](https://crates.io/crates/specs)) (still learning), no game engine.

Wait did the person at your company write specs or something else because they weren't pleased with it? I don't know much about amethyst and vaguely know about entity component systems but I watched a talk on someone making a game with amethyst and was pretty impressed -- it looked thoroughly approachable and I do not doubt the performance is there (since the whole reason you do ECS is performance).

You could also look at Entity Component Systems. Something like specs.

If you are making a game, instead of a game engine, you can have your cake and eat it too -

https://godot-rust.github.io/

Allows you to pair Rust with Godot comfortably via gdnative.

Then use one of the good ECS systems in Rust like -

https://github.com/amethyst/specs

or (archetype style ECS)

https://github.com/amethyst/legion

To get spun up on ECS in Rust I suggest -

http://bfnightly.bracketproductions.com/rustbook/chapter_0.h...

This won't get you a godot project but will get you a basic concepted game you can then port into godot-rust.

Fair enough on leaving parts up to other code instead of the library. I started my ECS with the idea of optimized storage (eg hash maps for sparse components) and indexing (which is why formal Not helps a lot, but indeed Maybe is only sugar for less code). I really liked this Rust ECS which also does parallelization, which makes it important for the ECS to also know which order the systems execute in, and their dependencies on each other (something I started doing but never finished): https://github.com/amethyst/specs