#Elixir#Chile presente. Comunidad tech por Chile 💚 #TechTon (23–24 ene): charlas en vivo + recaudación para Bomberos de la Región del Biobío. Stream: https://t.co/RSkm0cBekE Dona: https://t.co/GMO6MhyUtI
If you're looking to move away from Postman look no further (especially @elixirlang devs)!
Watch me take advantage of a lot of new features to show how easy it is to test APIs through Merquery.
You don't want to miss this!
You can find the repo here: https://t.co/GSA8pFKjGn
Man, coming from Javascript and React... Liveview makes so much sense!! My designer brain is getting every single part of it.
I found an amazing tutorial in Spanish building a mini job board with Phoenix LiveView.
A very good alternative to the Heroicons pack that comes by default in new Phoenix apps is https://t.co/KLc3zv4E0V – it includes many more icons and they look great! #MyElixirStatus
The wait is over - Fluxon is here! 🚀🚀🚀
A modern UI component library crafted for Phoenix Framework that delivers:
🎨 Sleek, modern design system
🌓 Dark mode out of the box
📱 Fully responsive components
🏗️ Ready-to-use layouts
#MyElixirStatus
🎉 Mind-blowing chat with @sorentwo on the podcast today! They just dropped huge news: Oban Web is going open source! 🚀 This is a massive win for the #Elixir community - the dashboard will be free for everyone!
Watch here: https://t.co/CkgEUu9Eog #elixirmentor#myelixirstatus
Given all the buzz around self-hosting lately, I decided to write a post on how I self-host my Elixir apps as a solo dev #MyElixirStatus
https://t.co/S6ODSqlfys
Elixir 1.18 is going to soft deprecate the `unless` keyword. I rarely ever used it tbh. It always felt more natural to me to just use `if !condition do` instead.
Pretty cool that they add a `mix format --migrate` command to have this autochanged.
Scripting with elixir is overlooked/underrated
@wojtekmach
created https://t.co/nKwhTjFE17… demonstrating how nearly any elixir package could be used in an exs script. Could be great where you want a simple script that you can run one time, but still leverage OTP, d/ets, etc
Enjoyed @dhh's appeal to simplicity and self-reliance in his Rails World talk.
It's well-known that @elixirlang's syntax is inspired by @rubylangorg's syntax. But it's less appreciated that the similarities run much deeper. Elixir has long valued a lot of the same things that Ruby has. One of those is a "batteries included" ethos.
For instance, both Ruby and Elixir have best-in-class standard libraries and a best-in-class web framework + ORM.
Elixir takes this ethos to the limit, though. Further than any other toolchain I'm aware of.
Ruby developers are well-aware that Elixir has an interesting model for concurrency. In the early days, Elixir/Phoenix was understood as a concurrent Ruby/Rails alt. Before I adopted Elixir, my mental model was "Ruby but with Celluloid/actors as first-class."
But that barely scratches the surface.
Elixir runs on the Erlang VM (BEAM). Packaged with that VM is something called the Open Telecom Platform (OTP). It's like having another standard library. Except this library operates a layer up from iterating over enumerables or performing mathematical operations. It's a complete toolkit for building concurrent, distributed applications.
At the core of that toolkit is the process. You can spawn a process, send it messages, introspect its state, get notified if it crashes, guarantee that it's restarted.
And here's the thing: practically every application and service is a concurrent, distributed system. For example, in all modern frameworks, each user request spawns some isolated thread/process/heap. Any time you have more than one server, you're in a distributed environment. Even if it just means a single web server node communicating with a Postgres database.
Erlang feels like it was built in a parallel universe, far from the JVM/.NET battle that influenced much of the landscape today. I think it's a miss that we built a generation of tooling without distributed primitives baked-in. When you see up close what it's like to build with OTP, it feels like a glaring, missing hole in other stacks. It's like a language missing file descriptors.
As a result, there's an extreme maximalism you can take with Elixir/OTP. You don't need Kubernetes, you have process lifecycle built in. You might not need Redis, you have ETS. You don't need to split your app into different services, you can create logical boundaries within a single distributed system. This maximalism breeds simplicity.
Or, stated in a single image (h/t @whizzaf):
How I built Algora TV as a solo dev
1/3 The same Elixir codebase includes the webserver, background jobs, cache, machine learning, orchestration, real-time webapp with @elixirphoenix and media pipelines with @ElixirMembrane
The Elixir Mentor Podcast was 🔥 today with @liltechnomancer! 🦄✨ We talked about turning ideas into real, useful projects 💡. If you missed it, check it out here: https://t.co/BetJwYkNFz #myelixirstatus#elixirmentor