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
The obligatory hello world thread!
Who are you and where are you from? :stuck_out_tongue:
New
@chrismccord : I just saw the Extract AGENTS.md from Phoenix.new into phx.new generator commit to the phoenix project.
My initial shotgu...
New
I was working on an Ecto migration and I needed a timestamp. So, for the nth time, I looked up the different data types for timestamps, a...
New
Fly’s CEO posted this recently - Turn And Face The Strange · The Fly Blog
It says that Fly is going all-in on sprites, which is a worry ...
New
We’re evaluating API mocking tools for OpenAPI-based projects and would love to hear what other teams are using.
We’re particularly inte...
New
Is there a word for the ~> symbol used in Version strings?
Do you also just call it a Squiggle Arrow™ ?!
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
Chat & Discussions>Discussions
Latest on Elixir Forum
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex











Showing Posts 1 to 10- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (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?