Re:Show HN: Coerce – Distributed actor framework in Rust
by Ygg2 on Saturday February 18, 2023 @08:04AM
(#34846615)
Without a top down mandate, what else can you expect?
In OSS ecosystems it's usually plenty of choices, or nothing.
See NPM registry or choosing DE in Linux.
Re:Show HN: Coerce – Distributed actor framework in Rust
by msdrigg on Saturday February 18, 2023 @08:39AM
(#34846854)
Within the rust ecosystem, rust has tokio as a clear winner for async runtime without a top-down mandate.
There are a couple of alternatives, but none of them come close in popularity
Re:Show HN: Coerce – Distributed actor framework in Rust
by mhluongo on Saturday February 18, 2023 @09:00AM
(#34846981)
Akka seemed to win in Scala
Re:Show HN: Coerce – Distributed actor framework in Rust
by the_alchemist on Saturday February 18, 2023 @10:50AM
(#34847747)
But then the main contributor, Lightbend company, decided to change the license from Apache 2, to BSL.. Now Apache Pekko is the fork that should continue the implementation :)
Re:Show HN: Coerce – Distributed actor framework in Rust
by jerf on Saturday February 18, 2023 @12:09PM
(#34848577)
There's a class of software project where it isn't very hard to bash together a simple thing that solves a good chunk of the problem, not covered by the language itself, but has endless elaborations you can put on them.
These rarely stabilize in the sense you mean, of there being exactly one sensible choice in some domain. (Note difference between "rarely" and "never".)
See also: Web framework, Javascript GUI framework, serialization libraries (easy to write the parser(s), endless combinations of ways to handle the resulting JSON for you), and these are just some big frequent examples that leap to mind. There's a lot of these sorts of things.
https://news.ycombinator.com/item?id=34813489
It feels like async / actor frameworks / gui things are permanently in flux. I wish clear winners would emerge already.