4 ms·

I've been following projects like Hotwire and HTMX for awhile now, and I haven't seen anyone argue that scraping is a major reason to adopt this approach. I als

I've been following projects like Hotwire and HTMX for awhile now, and I haven't seen anyone argue that scraping is a major reason to adopt this approach. I also don't see a lot of opposition to the idea of incorporating something like alpine to add some UI niceness. What you see as a "terrifying" disregard for "two decades of advancements", others see as a liberating departure from two decades of unnecessary bloat. It's healthy to have more than one strategy available for building web applications.

meiraleal 2y ago
> others see as a liberating departure from two decades of unnecessary bloat Is moving the bloat to a blackbox in the backend really a better approach? Why not just not create a bloated frontend?
- p_l 2y ago
  Because it might be in fact easier and simpler to implement it on backend?
  - meiraleal 2y ago
    it might, it probably isn't. Unless you only have a hammer.
    - p_l 2y ago
      What is, and what isn't easier has a big honking "IT DEPENDS" attached. And I have a strong suspicion for many the beloved hammer is big complex client-side JS framework.
- allknowingfrog 2y ago
  Using htmx allows you to completely skip a layer of JSON serialization and parsing. It eliminates the complexity of maintaining a second, frontend application, as well as all of its build tools and dependencies. It even opens up the freedom to work exclusively in your preferred language. All of these are examples of removing elements, not just hiding them somewhere else.