My (unproven) hypothesis would be that you could write the current in-flight tasks to disk and read them back on start up to kick them back off
Things you lose with this would be scheduled / future / cron, but that’s not my goal
I don’t need all the connections & polling for simple job retries. Database is always the bottleneck in prod. Elixir systems I’ve worked on. I think a stupid simple retry would serve most use cases
Oban is great and when the needs dictate the move to it, I’d move to it. It just seems there’s room for a smaller, simpler starting point
I’ve always felt like for simple job / function retry there was a lighter dep. you could bring than Oban
I think I can finally vibe code it now
All OTP primitives and file system….here goes nothin
AI is amazing at writing code. Amazing.
It's awful, and I mean awful, at organizing code
It makes sense when you know AI is just a _really good_ next word predictor
@mmmykolas@form Yes, checkbox + label can absolutely be styled to work with strictly the form
In practice, I find few devs I've worked with know you can style labels like that ;)
The Top 3 LiveView Form Mistakes (and how to fix them)
Prevent poor UX, brittle systems, and impossible states by using these 3 strategies.
https://t.co/Sm1CoFQ6qg
#MyElixirStatus
@bcardarella I think you'd benefit from https://t.co/g4qpghyghg -- Converts html to markdown & can execute JS, which is good for stuff like Apple's docs.
Apple docs can also be read by https://t.co/9v0xecfR0q MCP server