Very interesting and good to know! I've been keeping a closer eye on Rust lately as its beginning to look more and more like it would be foolish to ignore. Rust and Go have really made it hard to conceptualize where Elixir fits into the dev world these days. Go just seems to be a faster Elixir in a lot of ways. I'll keep an eye on this project and if you need any help - feel free to tag me on github (same username as this one)
> Go just seems to be a faster Elixir in a lot of ways
If you haven't worked with both, you just don't know. The developer experience in go is nowhere near the developer experience in Elixir. It's just so much easier to write scalable code in Elixir than Go. Sure it's not as fast, but it's not god-awful slow (speedwise, you're doing better than python django, for example), and for 90% of people shopping for what elixir and go offer, the network is the bottleneck.
To expand on that, the Go runtime is nowhere near the BEAM. To see why, check out this rant by a developer who has done a lot of work with Erlang [1], particularly starting at "Where it got really ugly for me".
I've only worked in Elixir. I think I just recently experienced some Go "fomo" because it seems to be more or less attempting to solve the same problem. I can't quite justify moving to Go from Elixir + Rust, but I'm always interested in hearing the community at-large take. Thanks for the response!
I've done both (Go first, actually), and I hated Go. And all of my dev friends who are still in goland have nothing but complaints. Small sample size (n ~ 3), but still.
Complaints I've heard: json broken, no good way to do orm, http library not great, no good framework for http webserver, etc. Channels/goroutines are deceptively hard, easy to cause resource leaks.
