Earlier quoted context omitted.
It's unfortunately accurate that a lot of roles and people in those roles are indeed purely bullet-point driven for their resumes. If you're entering a role at a mid-level or junior, you're likely stuck with their tech stack choices. At senior or higher, it's usually about delivering results and the tech stack is up to you. I've never paid much attention to specific job requirements, just whether or not I could solve…
The business risks surrounding unpopular choices are generally strong enough to overwhelm the technical arguments. So why should a lead choose htmx? IMO only if the project was trivial enough to bring on such whimsical risk.
The fact that a library which does nothing more than swap a DOM element after an XHR request has the entire React community forming a collective shield wall should illuminate why it’s a dead-end technology.