dimitrios

dimitrios

@dnlytras.com

husband, dad, && programmer. react, onyx, typescript, elixir, phoenix, gyarados blogging at dnlytras.com

54 followers32 following83 posts

Is there an estimate for phoenix 1.8? I was planning to start a new project, and I'm not sure if I should pull the trigger with the RC>

When building a Phoenix app, do you use the marketing name for your modules? For example: `defmodule MyAwesomeSaas.Something.SomethingElse` or do you prefer a generic name? like `MyApp`? I would hate it if I had to carry over an old name, and even more, renaming stuff down the road.

I really like TanStack Start. I feel like I'm getting nerdsnipped into building something new, along with better-auth. I'm not sure what to use for queues/jobs - that was always my pain point. I love how simple Oban is, and I definitely don't want to boot up a Redis instance.

Again, there's some good discussion in my post. I spend a good chunk of my non-work time (new father) studying Elixir, Phoenix, LiveView, and experimenting with them. I kept reading, "Just use LiveView," so I decided to try it out. I was surprised at how controversial my takes were.

Brian Cardarella@bcardarella.bsky.social

This is a very good hot take on Liveview dnlytras.com/blog/on-live... Many of my @elixirlang friends will immediately dismiss this a "hating" and they'd be wrong for doing so. #ElixirLang

The more I use Dependabot, the less I like it. I would much rather have a bot spam Slack every two days with the output of `npx npm-check-updates -i`. You spend so much time updating pointless patch versions with the illusion that you are fighting tech debt.

I'm not a fan of how everything is a `user_token` in the Phoenix auth generator. It's a very leaky abstraction. Why would I need `sent_to` in my session tokens? Imagine needing to add more metadata (IP, Browser, Etc) to sessions now. Almost always you have to separate them.

Finally found some time to try the Phoenix/Inertia/React combo, and I can honestly say it feels much better than LiveView to me. Heavy emphasis on "to me". I don't hate JavaScript. So to be able to use the fantastic Elixir ergonomics, with React, is a big win.

View full thread

Ultimately, the code feels less intimidating. `UserAuth.ex` is small, front-end code is properly colocated, and half of the changesets are now gone.

Finally found some time to try the Phoenix/Inertia/React combo, and I can honestly say it feels much better than LiveView to me. Heavy emphasis on "to me". I don't hate JavaScript. So to be able to use the fantastic Elixir ergonomics, with React, is a big win.

View full thread

Finally found some time to try the Phoenix/Inertia/React combo, and I can honestly say it feels much better than LiveView to me. Heavy emphasis on "to me". I don't hate JavaScript. So to be able to use the fantastic Elixir ergonomics, with React, is a big win.

My main grips were the js-hooks, and component organization in general. With Inertia I just pull all the good stuff from TailwindUI/Catalyst and move on.

Not sure how everyone's eslint 9 migration went, but for me it's a net negative. I still don't care about the configuration, docs everywhere are a mess, and the codemod broke half the rules.

Phoenix auth generator takes the most sensible approach. Fully transparent on what's happening. I can't fathom why would you want a library (Devise for example) take over your whole users table. You get some goodies, sure, but good luck debugging and patching that.

I'm debating if Liveview makes sense for me. It's a nice way to keep everything doing everything in Elixir, but I'm not too happy with the JS-hooks. I also don't like the confusing and duplicate code in on_mount. This is too easy to mess up, and I'm most certainly messing up.

Pushed some updates on my advent of code template: - Properly parse description as markdown - Optional follow-up with downloading the 2nd part when finishing the 1st Also finished the first challege #elixirlang github.com/dimitrisnl/a...

github.comGitHub - dimitrisnl/advent-of-code-elixir: An advent of code boilerplate using ElixirAn advent of code boilerplate using Elixir. Contribute to dimitrisnl/advent-of-code-elixir development by creating an account on GitHub.

I wish TypeScript had better error handling, and a Result type among others. But the more I used Effect, the more I had a non-standard codebase, with huge reliance on effect docs. So i cut my losses, used plain TypeScript, and moved to Elixir for the rest.

Before Claude and other AI tools, I wasted so much time tracking down subtle bugs, like typos. I would get into unproductive rabbit holes. Having them is such a great sanity check. - "Why is this test failing"? - "Well look at line X, ..."

Even though I enjoy TypeScript, removing prop-types from React 19 is sad to see. It leaves perfectly healthy codebases with a choice. Either have 0 hints, or transform your whole codebase. It's pretty unnecessary.

Well, Splitbee has been down for a day now, and I might continue like this. Thankfully I built a basic interface for analytics using Supabase and I can fallback to it. I need to move the tracking to middleware (Nextjs 15) if I find out how to filter out prefetch requests.

Anyway. I'm pretty fired about about RSC. It feels so nice now that I've tried it. My only issue is that I can't shake the feeling that I might mess up and leak something in the FE.

I'm unsure on what to write next. I have scattered thoughts on Next 15, Remix and Phoenix from various projects, but nothing groundbreaking

You are up to date.