José Valim & team have made such an incredible language and ecosystem. thank you for all the faithful work, especially the run up to 1.20 over this past year
Yeah. You'll notice that there's a mix of light and dark. Some segments are light-on-dark, then it switches to dark-on-light. It appears to me like a "design trend" that's at odds with accessibility. https://www.apple.com does this too.
>I also worked on all of the copy myself, collecting feedback from core maintainers as I went. The new tagline was a suggestion from Theo which we iterated on. I did use LLMs as an assistant, but I did not ask it to generate the content.
>Might as well use LLMs for the whole thing next time, since we will be accused of doing so anyway! :D
There are multiple people working on the JIT within the last 5-6 years. The WhatsApp folks also contribute meaningfully.
I suspect once the Erlang/OTP team squeezes all performance in the JIT, they will look into optimizing across modules, which will probably open up many new possibilities, but it requires rethinking some runtime primitives.
1. The cross module optimizations I mentioned above
2. Have a WASM target for the runtime itself
3. Make it easier to ship single file executables with the whole VM
But they are really “nice-to-have”s. I have been a happy user for 15+ years!
i ran a quick experiment where instead of doing boxing the way its done in the beam currently, i used a different boxing (NaN strategy and there was a 10x speedup
On the first syntax example: there’s something funny to me about using three pipe operator and four different functions to turn “hello world” into “Hello World”.
To me, it seems one of the killer use cases for Elixir (/Erlang) is its distributed cluster capability. Does anyone have experience with that or case reports to share? I've used Elixir quite a bit professionally, but mostly as just a "nicer Rails" with horizontally scalable but otherwise independent Phoenix apps in your traditional Kubernetes setup, which seems to me to kind of missing out on its main purpose.
It's been a while, but I used to work at WhatsApp and we used Erlang distribution heavily. I understand the clusters have gotten really huge since I left.
It's super handy. There's no security barrier between nodes. It's a headache if your network is unreliable.
For a chat app, messaging someone becomes a series of steps:
a) look up if they're online (send a message to the presence database service)
b) if you got a process id back, that's the process connected to the user, so send it the message. The process could be on the same machine or not, but the sending api is the same. This is the special part: few other environments make arbitrary messaging between processes/threads/tasks/whathaveyou so pervasive.
c) if you don't get a process id back, the user is offline; send the message to the offline database.
Also interested in hearing about this! I built an elixir k8s control plane recently and kept expecting to reach for it but it never really made sense when it was controlling golang daemonsets.
My usecase is less independent though, that control plane is orchestrating like Lambda/fly.io style workloads on top of firecracker:
https://jomcgi.dev/ember
I've worked a little bit with distributed Elixir using `Horde.DynamicSupervisor` on Kubernetes. Apparently there's other options like 'swarm' and DynamicSupervisor [1]. It'd be great for clear analysis of the benefits these kinds of abstractions bring vs non-BEAM approaches.
Elixir/Erlang works very well in a semi-embedded environment where you need a higher level command and control component that behaves in a deterministic way and is pretty robust.
I appreciate Elixir but the problem is the job market/talent pool is tiny compared to other existing languages.
If you buy into the Elixir stack then you now have constraint you could've avoided entirely by avoiding it.
Also for devs there seems to be no premium offered for this talent pool scarcity. With LLMs I think language-specialists are redundant in a large scheme of things. ex) at one of my current remote jobs, I shipped an entire telecom infrastructure with barely knowing Elixir and we brought on contractors to audit the code and they found no issues.
> appreciate Elixir but the problem is the job market/talent pool is tiny compared to other existing languages.
> I shipped an entire telecom infrastructure with barely knowing Elixir and we brought on contractors to audit the code and they found no issues.
Erlang/Elixir experience is rare, because it's not widely used and the teams are small. It's not worth trying to hire for it. Hire for people who can figure it out on the go (amd are willing to give it a try).
You did it, hire other people who seem likely to be able to.
i hired a biologist (for my pharma startup) and she produced feature ideas for our internal stack and was guiding claude to write idiomatic code with feedback from my reviews with no coding experience. realistically if you want to start an elixir company today you need one consciencious senior that likes code review and any number of juniors with minimal competency and sufficient curiosity.
Ugh, it looks like all the other LLM generated language webpages. It's formulaic at this point. I'd hoped a language like Elixir would be able to hire some people to do it.
The Software Mansion folks designed it and we actually iterated on the designs on Figma, having discussions as humans, and exploring alternatives. They were lovely to work with.
I also worked on all of the copy myself, collecting feedback from core maintainers as I went. The new tagline was a suggestion from Theo which we iterated on. I did use LLMs as an assistant, but I did not ask it to generate the content.
Might as well use LLMs for the whole thing next time, since we will be accused of doing so anyway! :D
Shame then that despite all that, they landed on the same design used by every "I asked an LLM to make me a language and a website this weekend here's what it spit out" project. I mean, I'm not saying it looks bad or is a bad result. Just it's very similar to other things that have put in much less effort.
I’m tried to understand the motivation for this salty comment and the parent comment. I failed. Then I opened the user’s comment history and most of their comments are like this. ModernMech, please, keep in mind we’re all doing our best. Being passive aggressive on the internet is social pollution. No offense intended, I’m just hoping you reflect a bit next time before you post.
It is funny (and perhaps a bit depressing) that LLMs were trained on our content and now, if we generate a similar structure as before, with the usual love and care, we will be criticized by it. Even when it does not "look bad or is a bad result".
Its pretty snappy/responsive for me at least so thats good. Normally LLM slop sites are pretty at first but sluggish as hell. So some level of skill went into this one.
If you must default to dark mode that’s your choice but I’d love to see a light mode toggle somewhere prominent.
The URL: https://elixir.hexdocs.pm/getting-started.html
I'm hoping to find a reason to use it soon.
(wip, no guarantees, this is the engine i use)
https://github.com/ityonemo/ce_ce
>Might as well use LLMs for the whole thing next time, since we will be accused of doing so anyway! :D
The only sloppy aspects that stand out to me are the needless animations/transitions.
Hoping Elixir continues to thrive. It is such a great language (and such a great language for AI coding too!)
1. https://arxiv.org/pdf/2508.09101
OT: I wish more funding & development effort went into BEAM itself on making it more performant.
Note: I’m not talking concurrency. I’m talking pure raw performance.
Seems like it’s been a one person show for over a decade on making it faster.
I suspect once the Erlang/OTP team squeezes all performance in the JIT, they will look into optimizing across modules, which will probably open up many new possibilities, but it requires rethinking some runtime primitives.
You’re an inspiration for many. Thank you.
I’m curious to know what your top 3 hopes for BEAM itself are for the coming years (in any area that you think would make it better).
1. The cross module optimizations I mentioned above 2. Have a WASM target for the runtime itself 3. Make it easier to ship single file executables with the whole VM
But they are really “nice-to-have”s. I have been a happy user for 15+ years!
You can get substantial performance improvements by using guards though. See what Wings3D does with is_float() everywhere in hot numeric-heavy code.
It's super handy. There's no security barrier between nodes. It's a headache if your network is unreliable.
For a chat app, messaging someone becomes a series of steps:
a) look up if they're online (send a message to the presence database service)
b) if you got a process id back, that's the process connected to the user, so send it the message. The process could be on the same machine or not, but the sending api is the same. This is the special part: few other environments make arbitrary messaging between processes/threads/tasks/whathaveyou so pervasive.
c) if you don't get a process id back, the user is offline; send the message to the offline database.
My usecase is less independent though, that control plane is orchestrating like Lambda/fly.io style workloads on top of firecracker: https://jomcgi.dev/ember
[1] https://www.youtube.com/watch?v=nZmDEUeHeVI
I was involved, years ago, in using Erlang on these devices: https://www.icare-world.com/us/product/icare-eidon/
It was a lot of fun and there were some very interesting challenges for everyone involved.
If you buy into the Elixir stack then you now have constraint you could've avoided entirely by avoiding it.
Also for devs there seems to be no premium offered for this talent pool scarcity. With LLMs I think language-specialists are redundant in a large scheme of things. ex) at one of my current remote jobs, I shipped an entire telecom infrastructure with barely knowing Elixir and we brought on contractors to audit the code and they found no issues.
> I shipped an entire telecom infrastructure with barely knowing Elixir and we brought on contractors to audit the code and they found no issues.
Erlang/Elixir experience is rare, because it's not widely used and the teams are small. It's not worth trying to hire for it. Hire for people who can figure it out on the go (amd are willing to give it a try).
You did it, hire other people who seem likely to be able to.
I also worked on all of the copy myself, collecting feedback from core maintainers as I went. The new tagline was a suggestion from Theo which we iterated on. I did use LLMs as an assistant, but I did not ask it to generate the content.
Might as well use LLMs for the whole thing next time, since we will be accused of doing so anyway! :D
If i go full dynamic, why not use pure erlang instead?
I hope you don't use discord or rely on pagerduty.