[asdfsa32]

It is different in that some of what happened on the frontend now happens in the backend, but overall, it is the exact same approach, so as I said in a sibling comment, it, it is just a second attempt at angular 1.0 with even more naive assumptions about web.

[wild_egg]

Based on skimming the couple sibling comments, I believe the issue you have had with htmx is precisely that you have somehow conflated it with angular. If you think they're the same, you will use them the same and have the same poor outcomes.

In another comment, you mentioned State Management. If this is on your mind then you are using htmx wrong. You should not be managing any client side state with htmx. State is on the server or in your database. Interactions on the client should immediately reflect the updated server state. If you have separate state on the client that needs to be managed, you are going to have a bad time regardless of framework.

[wredcoll]

> If you have separate state on the client that needs to be managed, you are going to have a bad time regardless of framework.

Yeah, because clients never need to keep track of state like which block is expanded or which tab is selected or that the previous page was or what the user is currently typing...

[wild_egg]

Every one of those are things that the browser manages for you if you are using semantic markup and embracing web standards.

[asdfsa32]

This is a pipe dream. Browsers have come a long way but they're largely still broken in many many ways.

[wild_egg]

Would love to hear about which of those listed examples does not currently have native browser support.

[asdfsa32]

> what the user is currently typing

Easy as pie. We don't even have to get into the specific of making things work correctly.