Several versions ago Jose talked about how Elixir is basically "done", which is so refreshing these days! But since then, the developer experience has improved by leaps and bounds through all these improvements other than the core language. As a professional Elixir developer for the last 4 years, I'm loving it. A few improvements in the last few versions off the top of my head that have been really nice: * Robust, ti…
Elixir 1.12
61–70 of 109 posts
Re: Elixir 1.12
#62Earlier quoted context omitted.
Sadly that HN thread is biased toward the person/team that is "leaving" Elixir because it wasn't a good fit for them. For the people who understand Elixir/OTP's strengths it's excellent. We use Elixir for several apps and haven't had any issues recruiting/training people (remote). If we were to chose again we would 100% pick Elixir; nothing else comes close for our use-case.
The point how all of Erlangs strengths are now obsolete because of XYZ that now exists misses the point how with Erlang/Elixir all of those things are at your fingertips using a single technology stack that is not hard to use and will scale very well for practically anyone.
I'm on my second team that has adopted Elixir and it has really helped our productivity being able to keep so many capabilities in one kit.
Re: Elixir 1.12
#63Several versions ago Jose talked about how Elixir is basically "done", which is so refreshing these days! But since then, the developer experience has improved by leaps and bounds through all these improvements other than the core language. As a professional Elixir developer for the last 4 years, I'm loving it. A few improvements in the last few versions off the top of my head that have been really nice: * Robust, ti…
Timex was never needed. We have a library Calendar.DateTime that has all the functionality we need
Re: Elixir 1.12
#64Re: Elixir 1.12
#65Earlier quoted context omitted.
I wish they'd instead fix the compiler to not require .then But in absence of that this is a huge QoL improvement. tap though... OMG yes!
I was very, very disappointed that the `tap` macro has nothing to do with pattern_tap: https://github.com/mgwidmann/elixir-pattern_tap Basically, in Elixir pipelines are not very friendly to simple destructuring: if a call at the beginning of the pipeline returns a tuple of `{:ok, result}`, you can't use either of shortcut syntaxes for lambdas (&Mod.fun/arity and &Mod.fun(&1)), you have to use `fn` and destructure in…
In my understanding, pipeline are mostly reserved for “unfailable” operations operating on raw data; whereas the where/else/do macro is more oriented towards errors handling; would it work better in your case?
Re: Elixir 1.12
#66Looking into Elixir, but from what i've heard, Elixir isn't very memory efficient when it comes to web servers. Is that still the case? Also where does one host Elixir apps these days? Heroku, Vercel or Bare metal?
https://bignerdranch.com/blog/elixir-and-io-lists-part-2-io-...
Re: Elixir 1.12
#67Earlier quoted context omitted.
Sadly that HN thread is biased toward the person/team that is "leaving" Elixir because it wasn't a good fit for them. For the people who understand Elixir/OTP's strengths it's excellent. We use Elixir for several apps and haven't had any issues recruiting/training people (remote). If we were to chose again we would 100% pick Elixir; nothing else comes close for our use-case.
The point how all of Erlangs strengths are now obsolete because of XYZ that now exists misses the point how with Erlang/Elixir all of those things are at your fingertips using a single technology stack that is not hard to use and will scale very well for practically anyone.
It helps you to add lots of tiny quality of life improvements to your product that you wouldn't bother with normally.
Re: Elixir 1.12
#68Several versions ago Jose talked about how Elixir is basically "done", which is so refreshing these days! But since then, the developer experience has improved by leaps and bounds through all these improvements other than the core language. As a professional Elixir developer for the last 4 years, I'm loving it. A few improvements in the last few versions off the top of my head that have been really nice: * Robust, ti…
> Mix.install This is game changing for me (my life is boring). I totally didn't even know this was coming. It's like unexpected Christmas! For folks not in the know, it's been kind of a PITA to have packages loaded in an Elixir repl without a proper project. This should enable a lot more developer tooling to exist too; I'm stoked because I have one tool in particular that's going to be immediately be useful thanks t…
Re: Elixir 1.12
#69Looking into Elixir, but from what i've heard, Elixir isn't very memory efficient when it comes to web servers. Is that still the case? Also where does one host Elixir apps these days? Heroku, Vercel or Bare metal?
I'm serving (https://domovik.app) for a few dozen people on a few dozens MB of RAM. Sure, it's not Google scale, but I really can't complain about memory usage.
Re: Elixir 1.12
#70Earlier quoted context omitted.
I wish they'd instead fix the compiler to not require .then But in absence of that this is a huge QoL improvement. tap though... OMG yes!
I was very, very disappointed that the `tap` macro has nothing to do with pattern_tap: https://github.com/mgwidmann/elixir-pattern_tap Basically, in Elixir pipelines are not very friendly to simple destructuring: if a call at the beginning of the pipeline returns a tuple of `{:ok, result}`, you can't use either of shortcut syntaxes for lambdas (&Mod.fun/arity and &Mod.fun(&1)), you have to use `fn` and destructure in…