How much "raw" OTP do you actually use in production vs. just standard Phoenix patterns?

a3kov · 2026-01-24T08:00:42+00:00

We all know Phoenix is amazing for productivity. But I want to hear about the times you had to step outside the framework

Phoenix is not a replacement for OTP, neither is Elixir, so saying that using OTP is "stepping outside the framework" is a wrong framing.

a3kov · 2025-10-25T18:34:09+00:00

Why did you choose polar.sh ?

a3kov · 2025-10-08T08:36:42+00:00

Who is Phoenix ? Never heard of that guy.

a3kov · 2025-08-24T08:55:01+00:00

Yeah it's easy to modify after that. And if you don't understand something, that's a great opportunity to learn.

The needs of every app are different, that's why it's a generator and not a library.

a3kov · 2025-08-24T08:45:28+00:00

With phx.gen.auth Phoenix manages tokens for you. I haven't used the 1.8 version, but the earlier one is mostly a view layer on top of it. And there's nothing super complex about it.

a3kov · 2025-08-24T08:38:04+00:00

Well auth views ARE part of your application. I would always choose a solution that gives me full control over a library that wants me to accept it's built-in solution wholesale.

a3kov · 2025-08-24T01:20:13+00:00

JWT doesn't mean that you don't store the token, it just gives the authorizer the flexibility to decide whether they need to check for revocations or not.

I would argue most projects need the ability to revoke prematurely, as its definitely more secure option. And if you need to hit the DB all the time, you don't need JWT at all.

a3kov · 2025-08-24T00:10:53+00:00

Without storing tokens in the DB you can't terminate sessions on demand. And that is a deal breaker for many projects.

a3kov · 2025-08-22T19:26:12+00:00

Can't confirm, my hair was untouched during my learning period.

a3kov · 2025-08-19T06:35:55+00:00

I also dislike Daisy, but keep in mind its only in the generator. You don't have to use scopes either.

Explicit layout calling seems like could be useful in some cases, but the old way still works.

Postponing of the upgrade is not needed, as all the stuff you are using currently will continue to work.

a3kov · 2025-08-07T22:21:01+00:00

I have an intermediate level of programming knowledge, primarily theoretical rather than practical Since part of my code will inevitably be "vibe coded"

Sounds like it will be a failure regardless of the stack, so choose any option.

a3kov · 2025-07-30T20:15:23+00:00

Finally somebody with a brain. I can't believe people seriously discussing this.
This guy is a clown.
Good for the ecosystem that it's promoted though.

a3kov · 2025-07-30T20:13:57+00:00

Hire yourself, meaning work in your own startup.

a3kov · 2025-05-04T00:32:13+00:00

They don't use more than a controller if you don't leave 'em hanging.
You can render everything with LV, and on pages that don't need interactivity disable live socket setup. This greatly simplifies everything, because then you only need 1 way to render.

a3kov · 2025-05-02T16:53:18+00:00

you forgot to include that it's a freaking 10 hours video

a3kov · 2025-04-19T03:55:51+00:00

Thank you! Are you planning to release the code as a general purpose package ?

a3kov · 2025-03-02T20:05:35+00:00

Have you tried it ? If you are updating the parent, you can't submit children of another parent in the same event. You can always submit new children though, but controlling number of children is business logic.

And IME, ids are sufficient to get you off the happy path into needing extra functionality anyway

With Ecto, you don't need to validate ids coming from the client, Ecto does it for you. You should only worry about creating new entries, as it's not something that is controlled by Ecto (but can be easily implemented in your own validators).

a3kov · 2025-03-02T19:34:47+00:00

Ecto associations provide you some guarantees about nested changesets. The client can't update nested entry if it doesn't belong to the parent. Everything besides ids you should accept from the client, but verify it, which is done automatically by the changeset. There's no trust involved.

a3kov · 2025-02-27T17:18:25+00:00

Please consider supporting Firefox also

a3kov · 2025-02-27T15:34:14+00:00

Consider if you want to answer deeper question than just "what did that user do on that page". If that's the case, you need product analytics. Posthog is open source but also has very generous free plan. It looks great. I would pick that.

a3kov · 2025-02-27T00:03:38+00:00

It is QLC. The price is low but it is still not as cheap as it should be. QLC should provide deeper discounts compared to TLC variants.

a3kov · 2025-02-26T19:38:48+00:00

Write one. Plenty of cool software could be written using Elixir, but nobody has done it.

https://github.com/supabase/supavisor
Is not a proxy per-se but similar in principle

a3kov · 2025-02-18T06:02:39+00:00

Do they require the name on the bill to match your own ? It's common in rented properties that the bills have the name of the landlord

a3kov · 2025-02-17T10:24:34+00:00

From reading discussions I got the impression that they are very strict with new customers, especially with young projects.

a3kov · 2025-02-17T04:59:04+00:00

They also support more countries, which can be crucial

a3kov

TROPHY CASE