htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext
htmx is small (~14k min.gz’d), dependency-free, extendable, IE11 compatible & has reduced code base sizes by 67% when compared with react
Honestly this is completely ridiculous. Hypertext using HTML constraints is absolutely insufficient for representing application state. It’s the wrong tool for the job and always has been, because it conflates document structure with semantic meaning.
Said another way, HTML cannot be relied on to capture a representation of application state.
The reason REST doesn’t use HTML in most contexts is because applications don’t use HTML in most contexts anymore.
Demanding that application representation use a specific encoding strategy is ridiculous and misses the point entirely, which is that HTTP is no longer the right protocol for the job.
While HTML is hypertext markup language, hypertext is not HTML.
Hypertext doesn’t imply a specific encoding strategy, it implies semantics - data contains links to related data. If you want to encode it in protobufs - you do you, REST explicitly calls for freedom in this regard.
To paraphrase yourself, ranting about HTML as if it was a requirement for REST is ridiculous and misses the point entirely.
Honestly this is completely ridiculous. Hypertext using HTML constraints is absolutely insufficient for representing application state. It’s the wrong tool for the job and always has been, because it conflates document structure with semantic meaning.
Said another way, HTML cannot be relied on to capture a representation of application state.
The reason REST doesn’t use HTML in most contexts is because applications don’t use HTML in most contexts anymore.
Demanding that application representation use a specific encoding strategy is ridiculous and misses the point entirely, which is that HTTP is no longer the right protocol for the job.
While HTML is hypertext markup language, hypertext is not HTML.
Hypertext doesn’t imply a specific encoding strategy, it implies semantics - data contains links to related data. If you want to encode it in protobufs - you do you, REST explicitly calls for freedom in this regard.
To paraphrase yourself, ranting about HTML as if it was a requirement for REST is ridiculous and misses the point entirely.
PS: HTML is not a protocol.