Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ractor
-
Write Elixir NIFs in Rust
This project also appears interesting, but it seems that its clustering features have yet to be tested in large scale distributed systems.
https://github.com/slawlor/ractor/discussions/131
-
A LiveView Is a Process
If you look at my comment history, you'll see I'm well familiar with the BEAM.
I'm in full agreement with you, but I'm not sure you need full robust process supervision trees to mimic what the BEAM does in the context of LiveView on a single machine.
I do want to say, I 100000% times prefer Elixir, it's tooling, ecosystem, web frameworks, easy of scaling vertically and horizontally, etc over Go or any other lang that probably do something analogous to LiveView via what ever concurrency primitives that language/runtime champions; Go with it's Communicating sequential processes(CSP) and Rust with the Ractor lib (https://github.com/slawlor/ractor).
-
Preferred way to receive events?
Also consider an actor framework like ractor. You can have actors listening to sockets, who will then message subscribed actor or actors with the data.
- Show HN: Ractor – a Rust-based actor framework with clusters and supervisors
- GitHub - slawlor/ractor: Rust actor framework
-
Ractor: not just another actor framework
github
golive
- LiveView Is Best with Svelte
-
A LiveView Is a Process
I think it is more exciting and more innovative to think about LiveView as a new architectural approach to building reactive applications. Yes in Elixir land it is a Process and there are some amazing things about the BEAM. But LiveViews have the potential have an impact beyond just the Elixir ecosystem and folks should embrace that.
I’ve been a part of porting the Phoenix LiveView Protocol to both Javascript (https://LiveViewJS.com) and Go (https://github.com/canopyclimate/golive) backends and supported a friend that is porting it to Python.
Ironically I think taking LiveViews outside of Elixir could actually make it easier for folks to adopt an Elixir in the future.
What are some alternatives?
zigler - zig nifs in elixir
pyview - A Python implementation of Phoenix LiveView
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
neural - NIF based erlang shared term storage
bastion - Highly-available Distributed Fault-tolerant Runtime
nx - Multi-dimensional arrays (tensors) and numerical definitions for Elixir
rustler_precompiled - Use precompiled NIFs from trusted sources in your Elixir code
postcard - A no_std + serde compatible message library for Rust
made-with-liveview - Explore the real-world potential of Phoenix LiveView through a showcase of impressive web applications.
lunatic-rs - This library contains higher level Rust wrappers for low level Lunatic syscalls.
crates.io - The Rust package registry