dimitrios (@dnlytras) / X dimitrios (@dnlytras) / X

Random, but I'm not posting here anymore. Consider connecting on twitter/x. x.com/dnlytras

Cheers!

Rails, Webpacker & React: A migration odyssey | Dimitrios Lytras Looking back at a painful refactor journey from Webpacker to Vite, Enzyme to React Testing Library, and React

New post ✍️

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>

I agree. For something like zod, dayjs, I completely skip the readme/repo and go straight to the docs/website.

For smaller stuff like react-hot-keys, a well-organized readme gives me the same confidence, as most website sections are tiny.

local first let's goooooooo

Would a very comprehensive readme make up for the lack of website?

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 cloned the inertia repo a few minutes ago. A lot of good stuff, but I can't be arsed to write the register/login/forgot-pw/reset-pw flow again.

Having something like this and, adding Inertia on top is a killer combo. You practically eliminate all the paid boilerplates.

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.

"Please generate a Studio Ghibli image of me dunking over redditors"

Very happy with your success. I remember reading some of your articles back in the day. Very happy that you had your breakthrough - keep it up!

I would love that, probably not pure white, greyish as you said. I'm in between things right now, I'll add it to the backlog!

Anyway, the post has a specific target audience. People who evaluate alternative front-ends (Turbo, LiveView, LiveWire, etc).

You usually don't get the other side of things. I tried my best to give one for LiveView.

It's ok.

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.

Thank you for the kind words.

I literally fixed a bug with useEffect moments ago, feeling dirty the whole time. Crazy to have such a disgust against an API.

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.

Most random decision. Couldn't pick a worse platform. No heads up as well.

If I had to split it then remix and phoenix no questions asked. Next has so much friction I don't find any value.

I experiment with inertia to keep phoenix as backend but react in the front. All with the same pipine. I don't like next or remix for true backend work. Remix for example can't support multitenancy in a stress free way.

Thank you for the sanity check as well, lol

Just published my zed theme. Check it out if you want, search for "Lydia" in the extensions

#elixirlang !

Using Phoenix with React and Inertia | Dimitrios Lytras Getting the best of both worlds; Phoenix's productivity, and React's ecosystem

Some thoughts on my experience with using Inertia and Phoenix!

dnlytras.com/blog/phoenix...

My experience with Phoenix LiveView | Dimitrios Lytras Some takeaways from my time with Phoenix LiveView

I wrote a bit about some issues I've faced when working with LiveView dnlytras.com/blog/on-live...

Lol same boat. Same version. Feeling validated.

Streaming OpenAI responses The home for Phoenix-oriented content ranging from Ecto to LiveView and more.

I was referring to actual HTTP Streaming, like here fly.io/phoenix-file...

Component organization and rapid prototyping are something I value, so I'm in the same boat.

If you want websockets or streaming nothing is stopping you from using them. You lose the HTML diff'ing that comes with LiveView. You still use Phoenix as a backend.

2. Inertia is popular, especially in the Laravel world. I've relied in the past on niche libraries that do some plumbing between technologies, and every time I got burned. I also don't want Liveview at all - it's a lovely technology that doesn't fit my needs.

Two reasons:

1. I evaluate Inertia for other uses as well. I recently migrated a Rails backend from the deprecated webpacker to Vite, but Inertia is still an option to simplify things further.