I choose Rails for fast prototyping, recently Go if I want pure performance that I can't get from caching, and Elixir + Phoenix if I need a good concurrency model and/or high throughput, but don't necessarily care about…
Elixir + Phoenix seems like a better choice if websockets is going to be a core feature, since the BEAM's concurrency model is better and Phoenix's "Channels" abstraction is so solid. I wouldn't think of using Rails for…
A little off-topic, but I figured the people reading the comments here would be the best place to ask. Why use JavaScript on the server at all? I've developed on both the front end and back end, and written non-trivial…
I choose Rails for fast prototyping, recently Go if I want pure performance that I can't get from caching, and Elixir + Phoenix if I need a good concurrency model and/or high throughput, but don't necessarily care about…
Elixir + Phoenix seems like a better choice if websockets is going to be a core feature, since the BEAM's concurrency model is better and Phoenix's "Channels" abstraction is so solid. I wouldn't think of using Rails for…
A little off-topic, but I figured the people reading the comments here would be the best place to ask. Why use JavaScript on the server at all? I've developed on both the front end and back end, and written non-trivial…