Trending in Discussions
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
New
Hey there,
It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Quite interesting article Google brought me. Didn’t find any mentions about it here.
What do you think in general? Would you use togethe...
New
Since we have deprecated our Erlang sections (as we have dedicated Erlang Forums now) let’s add this thread for those who’d like to post ...
New
:warning: Security advisory: Decimal DoS vulnerability
A vulnerability has been published for decimal where very large exponents can cau...
New
What IDE or editor are you using for Elixir development?
Personally, I use Zed, and I really like it, but sometimes I wish there were a ...
New
Other Trending Topics
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Aludel - LLM Evaluation Workbench
Aludel is an embeddable Phoenix LiveView dashboard for evaluating and comparing LLM prompts across mult...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lkuty
I am trying to follow new versions of Elixir and Phoenix, refactoring code as needed. So I am at 1.18.2.
cmo
1.18.4-otp-27
tfwright
Just upgraded to 1.18. I try to stay 1 behind current.
binarytemple
Pet project:
Elixir 1.19.1-otp-28
Erlang 28.1.1
Both seem like great releases
NobbZ
We are trying to keep up, though had to skip 1.17 for a bug that never has been fixed in any release if the branch, but actually got backported onto the release support branch.
Now we are working on updating to 1.19 from 1.18, though the deprecation of strict update makes this update non trivial.
dbaer
We are running a couple small but customer facing applications that are still on Elixir 1.12 since it’s inception. The majority are on 1.15 and our flagship is currently on 1.17 which will soon replace most of the smaller systems, and be upgraded to 1.19 early next year.
Edit: also an internal system still used daily that is running Elixir 1.8 which I haven’t touched since upgrading from 1.7. Can’t believe I forgot it since it’s one of the most critical. If it ain’t broke, don’t fix it as they say.
sevenseacat
Current work project:
elixir 1.18.3-otp-27
erlang 27.3.4.2
dimitarvp
Most of the time staying on current but sometimes had to stay 1 major version behind.
I think I missed this one, can you give an example or point me to docs?
NobbZ
You missed the deprecation of struct update, without matching on the struct first for the type checker?
In the first RC it was a full deprecation of
%S{s | a: :new }but now we have to convince the type checker first thatsis indeed anSsince the second RC IIRC.dimitarvp
Oh, that. I saw it on the forum but I could not switch to 1.19 at the time. Thanks for the reminder.
What was the proposed workaround?