Is PETaL stack still relative ?

[plush wedge]

I’m devoloping an CRM like project and I’m pretty new to Elixir, the experience so far is great but I see myself spending more time one UI components compared to UI frameworks like React. I am considering to simplify the UI work with Phoenix if Alpine is still a good choice for it.

I’m trying to stay native as much but I’ve seen PinesUI which i is really similar to shadcn in visual terms which uses Alpinejs

I see that PETAL was relative for like 1-2 years ago, my question is should I include Alpine in my project ? Or did JS interoperability improved since the stack came around and there is no need for alpine for easy client-side interactions.

I did build a few simple components with hooks & css and it was not hard at all but I don’t want to miss another world.

Thanks !

[plain glen]

Personal project or business?

[thorn onyx]

I don't think there's any reason to not use alpine.js any more, it's still a good tool. There's even the Petal framework (https://petal.build/) that is built with it. I think it's just not talked about as much due to the Phoenix.LiveView.JS doing a lot of easy stuff, and hooks handling the rest. I personally played with it, but have yet to find a real use for it.

[plush wedge]

Personal project yet I want to scale up the operation in some time if it becomes successful in 1-2 years

[plush wedge]

Yeah I've seen the petal.build, yet I'm not interested to put in some money on UI components when there is a lot of free ones. (even there is few for phoenix)

Is it easy to mix&match the LiveView.JS and the AlpineJS ?

My worries is that at some point there will be incompatibilities between the engines and will hit a harder bottleneck after some time devoloping the app.

[royal jackal]

I would skip Alpine until you actually require more frontend-only stuff than LiveView JS feels convenient for.

I did have a bunch of weird fights between Alpine and morphdom way back.