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?

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.

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.

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.

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

#elixirlang !