The article "Less htmx is More" reflects on the author's two-year experience using htmx in web development, emphasizing a minimalistic approach for improved user experience and maintainability. The author advises relying primarily on HTML and utilizing htmx selectively for specific page updates.

Key Points:

• Approach to htmx:

  • Emphasizes using plain HTML for most website functionalities.
  • Suggests htmx for updates users don’t expect to see on a page refresh and updates that remain on a page refresh.
  • Recommends standard links and forms for full-page navigation, preserving a logical URL structure.

• Critique of hx-boost:

  • hx-boost transforms normal links into dynamic ones mimicking single-page applications (SPAs).
  • The author advises against hx-boost, citing issues like partial updates and incompatibility with other JavaScript libraries.
  • Advocates for regular links to maintain reliable UX and developer experience.

• Alternatives to hx-boost:

  • Use browser caching with headers like cache-control to optimize load times.
  • Utilize browser capabilities that preserve consistent performance on page navigation without complex scripts.

• Performance and Browser Features:

  • HTML provides inherent performance upgrades as browsers evolve; leveraging these can remove the reliance on complex JavaScript solutions.

• SPAs and Trade-offs:

  • SPAs are complex and not recommended for simple interactivity enhancements.
  • They should only be used when necessary for specific functionalities, like maintaining a persistent state across navigations.

• Conclusion:

  • Suggests that htmx is beneficial when used properly but requires understanding of when and how to implement it.
  • Highlights the importance of prioritizing HTML and HTTP for web functionalities, considering ease of use and longevity.

The article also mentions upcoming HTML proposals like Triptych that may further streamline web development processes.