I would recommend https://data-star.dev over htmx. It is more complete. But it depends on what you are building. Datastar does everything that htmx can do and much more.
It doesn't have history support out of the box. I consider that essential for hypermedia apps. When I'm loading fragments into my page I need to push the URL of the fragment I just loaded so the user can reliably come back to that specific resource later.
I've spent my entire 30 career in ERP Consulting (PeopleSoft), working with Payroll, Accounting, and Student management systems.
I have a current client that is a mirror of this exactly. They had one new executive go to a sales demo, and the sales guy told him it would be "live" in a few months, and he believed it. It was so laughable and downright embarrassing for the client. In this case, I know it is at least a 3-year project if you have competent team members and vendors. It also depends on how you define "success" and how many business processes you are willing to break. However, these can stretch into 5 year projects when you are working with mission critical systems running accounting and payroll. In those cases, you cannot move fast and break things.
Most organizations don't have competent teams, and the vendors are often made up of low-skilled offshore workers, which makes nuanced, complex projects very complicated. The sales side will promise the world then the implementation team is low skilled and underdelivers.
I have seen this with several other clients, replacing pieces of PeopleSoft modules with different applications. Sometimes they come back and sometimes they just suffer through it and then find a third option after the new system fails to deliver.
Most ERP systems are just CRUD systems. So, you end up with a working CRUD system being replaced by a new CRUD system. The old system had its strengths and weaknesses. The new system will solve some problems and break others.
You spend 3-5 years replacing a system only to end up in the same place you were before: A CRUD system. This is maddening unless you are the new vendor and getting enriched.
I tried obsidian but felt it had too many gears and knobs and spent too many times fiddling with them. I fell back on this app which is based on local markdown storage but takes it up a notch.
I stopped using Postman years ago because it got too bloated an "enterprisy".
Also the fact that it syncs all my stuff to the cloud across many consulting clients is a no go. Passwords and other stuff means it is a target for hackers.
Postman is a great product don't get me wrong but my specific use case are around HTTP testing and I want to check everything into version control
