21–30 of 31 posts
Since this was written about 8 months ago. Our Elixir/Phoenix service has been incredibly stable and I can't think of a single time we had an issue with it.
Have you considered moving the logic that is in the Node backend over to phoenix, so you just have a single backend component?
Earlier quoted context omitted.
Sometimes I want partial application and other functional paradigms... to reduce LOC by 90%
I’m currently in the process of picking up elixir. When you say partial application, are you referring to the use of the capture operator `&`?
Though that alone can't reduce LoC by 90%. Elixir is just incredibly terse and no-bullshit language in general. All the shorter code idioms together make for a readable and to-the-point code.
Earlier quoted context omitted.
Sometimes I want partial application and other functional paradigms... to reduce LOC by 90%
I’m currently in the process of picking up elixir. When you say partial application, are you referring to the use of the capture operator `&`?
In Elixir when I want to pass a function with 3 arguments into an interface that expects 4, I can do something inline with no extra boilerplate like func(&1, &2, &3, )
Why not use Go? They have one of the best networking stacks among language standard libraries, excellent support for low latency soft real-time concurrent operations, and single binary deployment is trivial.
Since this was written about 8 months ago. Our Elixir/Phoenix service has been incredibly stable and I can't think of a single time we had an issue with it.
Since this was written about 8 months ago. Our Elixir/Phoenix service has been incredibly stable and I can't think of a single time we had an issue with it.
The Elixir repo on github hasn't been touched in 7 months. It's been that stable and feature complete?
Earlier quoted context omitted.
The Elixir repo on github hasn't been touched in 7 months. It's been that stable and feature complete?
Which elixir repo? the elixir-lang repo last had a commit 3h ago. the phoenixframework repo was update last week
Why not use Go? They have one of the best networking stacks among language standard libraries, excellent support for low latency soft real-time concurrent operations, and single binary deployment is trivial.
Not OP. Very personal opinion: Go is an ugly language and I don't enjoy working in it for that reason alone. Outside of that, I also don't like the language design for a lot of its features. Though, admittedly, the goroutines part is not one of those choices I dislike. But the error handling pattern, generics and a few other things are super meh to me. And everything Go does with networking and concurrency, Elixir do…
Why not use Go? They have one of the best networking stacks among language standard libraries, excellent support for low latency soft real-time concurrent operations, and single binary deployment is trivial.
go is great at a lot of things but if you want a multi clustered websocket solution, elixir is the absolute best in this category. go has go threads. elixir has the actors, futures, message passing, immutable data structures and the OTP platform. OTP is killer and gives you genservers with pubsub and the ability to have thousands of tiny stateful processors PER machine. Its all battle tested too. comparing go to elix…
Go has this too. It also has message passing (via channels). That's not to deny that Elixir/Erlang have a more developed story for IPC, process supervision and clustering.