A #datacube viewer for #biodiversity and #carbon dynamics built with #ElixirLang #phoenixframework and #maplibre - seen at #lps25 by folks from Estonia | #geospatial
A #datacube viewer for #biodiversity and #carbon dynamics built with #ElixirLang #phoenixframework and #maplibre - seen at #lps25 by folks from Estonia | #geospatial
There was a comment under phoenix.new ann on reddit that it makes no sense because there's not enough #ElixirLang code out there for LLMs to be trained on thus results are poor - wanna debunk that right now.
Yes, there's definitely more JS or Python code out there but clearly there was already enough Elixir code for LLMs to become *really good* at generating it.
Now AI editors can read docs and use MCP tools to help themselves, which changed the rules of the game.
That's why the amount of training code data is probably no longer that important.
I use Claude 4 and I can tell you that it crushes every task I throw at it in my pretty complex Phoenix apps. It writes great tests, it can perform tough refactorings, and it's pretty good at debugging too.
With tidewave Claude 4 became even more effective at writing Elixir simply because it can figure things out by using iex, inspecting logs, looking at db via Ecto etc.
Personally I hope that phoenix.new will eventually become an extension that I can use locally, but it doesn't change the fact it's an important and good initiative that makes perfect sense and probably has a strategic meaning for the Elixir language.
#ElixirLang #PhoenixFramework #AI
https://www.reddit.com/r/elixir/comments/1lg73s6/phoenixnew_the_remote_ai_runtime_for_phoenix/
How do you implement multi-step forms in LiveView? I have a LV that coordinates its "step" live components (and they may or may not have their own live sub components) and I find this setup quite complex. As always, handling state is the tricky part.
*Some* state from a step needs to be passed to the next step, and then the user may want to go back and make changes and go forward again. What's your strategy in cases like this?
I also need to deal with async processes and report progress in the UI, when a sub-sub-component triggers it, the parent LV receives an update and it has to route it back to the sub-sub-component, which is messy for my taste.
So, same question - what's your approach?
Phoenix 1.18 is going to ship with support for https://daisyui.com. I wonder if upgrading might be a good opportunity for Keila to switch to daisyUI as well. Spruce up the UI a bit, simplify the markup, and finally add support for light mode.
Do any of you have thoughts on daisyUI?
New screencast!
"Vibe Coding a feature in my Elixir Phoenix app - 100% real Cursor AI experience"
This is an over hour long session when I just sat down and told Cursor to build automatic CHANGELOG.md updates in my upcoming RepoBot app.
Check out the completely revamped API documentation, now using scalar.com instead of the old Swagger interface: https://app.keila.io/api
I’ve also just added a new API for signup forms and for creating contacts with Double-Opt-In.
The OpenAPI schema is generated (and validated) using open_api_spex and the docs page is simply a static page that includes the standalone.js script from Scalar.
I think I’ll switch the Keila API docs (https://app.keila.io/api) from Swagger to Scalar. It just looks much cleaner and more professional.
Any Phoenix devs who have done this already with Open API Spex?
I'm clicking on a web app on localhost, and then I'm clicking on the same app deployed, and I just see no difference. Both feel like it's localhost.
Gotta love Phoenix + LiveView and "Sent 200 in 785µs" responses
I REALLY don't want to join #Bluesky and love it here on the fedi. But people keep telling me I just won't find enough people here to follow and engage with.
If you love #linux #WebDevelopment #php or #elixir #elixirlang #phoenixframework drop a comment here and retoot so I can follow you.
I really love the community here and want to find my people. :)
@slightlyoff Working with #phoenixframework LiveViews is such a breath of fresh air. No JS, no npm dependencies, tiny footprint, but I can go seamlessly between pure HTML/CSS pages and fully interactive SPAs while doing everything on the server side.
Here's my current @justcrosspost stack:
- https://elixir-lang.org
- https://phoenixframework.org
- https://getoban.pro
- https://tailwindcss.com
- ETOOMUCH Vanilla JS - so I'm exploring SolidJS/Svelte/Preact as a remedy
Welcome Twitter migrants! I guess it's a good time for an #introduction
I've been creating #videogames since 1994 on all conceivable platforms. These days, I am a consulting CTO for a fintech startup, as well as part of a tiny indie game studio.
I mostly work with #elixir #phoenixframework #ruby #rails #unity #csharp and have a passion for #functionalprogramming #fp.
Currently writing a book on building a scalable multiplayer game server with Elixir.
If you are just starting out with Phoenixframework, spend some time learning elixir. Just enough for you to get going. Dont worry too much about OTP.
Once you have a good grasp of processes and message passing you are on your way to understanding GensServers and OTP.
Make apps. Learn incrementally. Review documentaion from time to time. You will find you it takes a few tries to understand some concepts and that is ok.
Happy learning
#elixir #phoenixframework
Sentry tracing for Elixir/Phoenix/Ecto update:
Live view traces
Ecto db statements in traces
Getting there!
Great progress on supporting Traces for Elixir/Phoenix/Ecto in Sentry! Gotta clean things up and add way more tests but this is looking good
I have to admit: The more I learn about #phoenixframework and #Elixir, the more I like it, the more I want to work with that. Although holy shit has frontend webdev become complex.
Hey look, we just shipped Honeybadger Insights. Logging and observability for your web apps.
I'm so excited—and there's much more to come!
https://www.honeybadger.io/tour/logging-observability/?utm_source=mastodon
Playing around with #elixir #phoenixframework #liveview as a platform for browser games.
This is a proof of concept for driving animations with server-managed state and pushed events.
Most of this is bog-standard LiveView functionality with two small JavaScript hooks acting as glue for forwarding transitionend events and applying transitions generated by the server.
The more I learn about #elixir #elixirlang and #phoenixframework , the more I'm impressed by how powerful, yet flexible it is.
My brain, steeped in 20 years of #php experience is still struggling with the syntax, Marcos, and the whole functional paradigm. But I imagine that gets better with time