Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
ponyc
Pony is an open-source, actor-model, capabilities-secure, high performance programming language
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
moleculer-rs
🚀 Progressive microservices framework for Rust, based on and compatible with moleculerjs/moleculer
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
I mean, if you just copied erlang exactly, you'd at least have erlang-in-rust (which is what rustler seems to do)
Speaking as someone who has used Erlang longer than most, who created a pre-Elixir-like language for Erlang's BEAM VM, and who routinely listens to Carl Hewitt's rants about why Erlang actors are bad, and who tried to make a Ruby actor library after using innumerable other library-level actor solutions...
Speaking as someone who has used Erlang longer than most, who created a pre-Elixir-like language for Erlang's BEAM VM, and who routinely listens to Carl Hewitt's rants about why Erlang actors are bad, and who tried to make a Ruby actor library after using innumerable other library-level actor solutions...
Yeah like I mentioned I'm not like super sold on the everything-should-be-an-actor paradigm, but I find value in DDD + a light implementation of Components (similar to stuartsierra/component).
Thanks for the insight -- I personally can see benefit in remaking Erlang in rust just for the strong typing. At present I only know of Gleam which is typed Elixir and don't know any typed Elixir. I like types very much, and Rust is basically second to Haskell in my mind for expressive type systems that I like using.
Does that one even count, in the absence of some sort of macro to write all the boilerplate? ;)
For actor centric programming, I'm more interested in Pony than trying to build actors in top of Rust, where most actor abstractions feel a little clunky and out of place.
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 can see it here: https://github.com/primcloud/moleculer-rs
Here is the protocol I implemented in rust: https://github.com/moleculer-framework/protocol
Would love to. I built a rust client for the moleculer microservices framework
One more Actor Model implementation for the list: https://github.com/sergey-melnychuk/uppercut
Personally I know all this from digging around in libponyrt, writing some bad Pony code and spending some time in the Pony community.
I always thought that crates.io should impose a minimum crate name length requirement, eg 16+chars, and require community voting for shorter names for easily discoverabilty for popular projects. ( so 10+ projects all have lengthy names.. and eventually when one gains traction it can be renamed plain "actors-rs" or whatever
I've saved a link to distillery just in case, cheers.
I guess lucet could be an under-layer for this but it's not really the same, different levels of the stack. Fascinating.