Chris James -HTMX is the Future
quii.dev · 3,689 words · saved by 1 readers
Chris James, London - Software Engineer
The current state of web application development User expectations of the web are now that you have this super-smooth no-reload experience. Unfortunately, it's an expectation that is usually delivered with single-page applications (SPAs) that rely on libraries and frameworks like React and Angular, which are very specialised tools that can be complicated to work with. A new approach is to put the ability to deliver this UX back into the hands of engineers that built websites before the SPA-craze, leveraging their existing toolsets and knowledge, and HTMX is the best example I've used so far. T
saved by
related reading
- The new wave of Javascript web frameworksfrontendmastery.com
- Single-Page Application Architecture | Ramotion Agencyramotion.com
- 7 Principles of Rich Web Applicationsrauchg.com
- RSC From Scratch. Part 1: Server Components · reactwg server-components · Discussion #5github.com
- Web Applications 101 - Robin Wieruchrobinwieruch.de
- Dynamic Web Apps without JavaScript - HTMX Showcase at DjangoCon and Devoxx - InfoQinfoq.com
- Pure UIrauchg.com
- The Elements of UI Engineering — overreactedoverreacted.io
- Navigating the future of frontendfrontendmastery.com
- How building an HTML-first site doubled our users overnightmohkohn.co.uk
- Extensible Software in the age of LLMs | Jeremy Morrelljeremymorrell.dev
- Making Sense of React Server Components • Josh W. Comeaujoshwcomeau.com