What do you think of Livewire and Inertia.js?

Question

Frontend

Recently, Livewire and Inertia.js have been gaining popularity in the Laravel community as components for server-side front-end generation. I see a lot of articles and tutorials, and in the latest Laravel installer, they generally brought a choice between them.

I would like to read the experience of those who already use them in the sale. What are the pros, cons, pitfalls? Are they stable enough? How smoothly does the transition to new versions go? How do project owners on github behave? etc.

PS Yes, I know that a monolith is bad. Yes, I know that it is better to take out the front in a separate project. In this question, I'm only interested in these 2 components.

Answer 1

I will say almost nothing about inertia. About livewire - For mvp, low-budget startups, indie projects, what is the default for a limited audience and should not be too loaded, some kind of admin panel ... is quite an option.
For more serious things and with a view to the future, I would stay on proven technologies.
Of the pitfalls - from the technological side - a wild confusion of responsibilities. From a practical point of view - every sneeze changes in the interface - the same counter button, changing tabs, or something else, implemented without Orthodox scripts - these are requests to the server. And one more thing - a serious locking on these technologies, their updates.
Specifically, tailwind did come in for me, if I cook it wisely and take out sets in scss. In a company with purgecss, you can get a very light css file as an output. But he is always in the company with components - a blade, or js frameworks (And this, of course, from the position of a backender. If there is a front manager on the project, then he should rule the ball).
In any case, I would advise not to rely only on the opinions of others, but to twist and feel everything yourself. At a minimum, they are on a hype, which means that there is a chance that you will encounter them sooner or later anyway.