Earlier quoted context omitted.
I've never tried it but I think I've heard of it. Regardless, it's a third-party tool, so not at the same level of support as Go.
Technically ecto, phoenix, plug, cowboy/bandit and Jason are third party tools too.
Adding Elixir to our Nextjs app (2022)
11–20 of 31 posts
Re: Adding Elixir to our Nextjs app (2022)
#12Why 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.
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 does better.
Elixir just doesn't have the backing of a big name like Google so it doesn't have the same popularity.
Re: Adding Elixir to our Nextjs app (2022)
#13Why 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.
Re: Adding Elixir to our Nextjs app (2022)
#14Earlier quoted context omitted.
Technically ecto, phoenix, plug, cowboy/bandit and Jason are third party tools too.
Yes, I'm aware. I've been programming in Elixir since 2014. I didn't intend to imply that being third-party means these are bad tools, they're not. They're great. But Go people often harp about how much stuff is in the standard library, so it felt relevant to mention.
Re: Adding Elixir to our Nextjs app (2022)
#15Why 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 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 elixir in this particular case is like comparing a piper cub to a jet liner
source: 5 years of experience building an elixir startup with realtime sync between devices over websockets as a killer feature.
Re: Adding Elixir to our Nextjs app (2022)
#16Would have loved to have seen a section devoted to what feedback you heard, what the team member's poor experience was, and how you felt confident that Elixir & Phoenix would solve those problems.
Re: Adding Elixir to our Nextjs app (2022)
#17Why 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.
Re: Adding Elixir to our Nextjs app (2022)
#18Why 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.
Re: Adding Elixir to our Nextjs app (2022)
#19Why 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.
Sometimes I want partial application and other functional paradigms... to reduce LOC by 90%
Re: Adding Elixir to our Nextjs app (2022)
#20Since 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.