The only issue I have with those tools, and I have not seen a single one even acknowledge this, is that it becomes completely useless when holding meetings in a hybrid fashion where some people are remote and others are in the office with a shared mic.
Almost all of our meetings are hybrid in this way, and it's a real pain having almost half of the meeting be identified as a single individual talking because the mic is hooked up to their machine.
It's a total dealbreaker for us, and we won't use such tools until that problem is solved.
Not everyone needs to achieve success (whatever that means) before their thirties. It seems like the spotlight will always be on the young blood revolutionizing a particular sector.
Most entrepreneurs don’t reach success, or even launch businesses, before being well into their thirties and forties.
The point being is that new hires will bring fresh eyes to an organization, whereas the team in place might be numb to some of the issues.
You don't need a new hire to fix those problems, but it certainly helps shed new light on some problems. Especially if you are hired as a senior dev or a team lead, you will be expected to fix some of those things.
LiveView goes far beyond what htmx offers. Or at least makes it much more fully integrated across the whole stack.
htmx is a frontend library first and foremost, that dictates some patterns you may want to implement on the backend. LiveView is a backend-first framework, with excellent support for interactive frontend stuff.
Phoenix LiveView handles all of those concerns extremely well and pretty much for free. All of my modals are tied to a live action in a given live view. You can bookmark them, use the browser back button to close them and the state "under the modal" is a complete non-issue. It's just loaded as part of the live view and a modal is shown only on specific actions.
That may sound like gibberish if you're not familiar with Phoenix LiveView, but it all makes sense and it just works.