Hotwire

All 253 user comments originate from HackerNews and discuss Hotwire as a web development framework — NOT the hotel booking service. The discussion is deeply technical and polarized. POSITIVE: Users praise the elimination of a separate frontend project ('saved me a lot of time and frustration having to deal with a separate frontend project'), the minimal JavaScript approach ('Turbo has client and server side components that enable easy ways to do partial page refreshes without writing any js'), and the philosophical return to server-side rendering. One user calls it 'the canonical way to do this sort of stuff with Rails now.' NEGATIVE: Multiple users report severe latency sensitivity — state changes require server round trips, making it unsuitable for high-latency environments. A paying HEY customer (Basecamp's own Hotwire-built email app) reports: 'On a slow connection, it's bad... stuff behaves in an unpredictable/buggy way. Boxes open with no content. Links don't work like you'd hope.' Offline support is identified as a fundamental weakness compared to SPAs. Complex UI patterns like dynamic nested forms are described as frustrating to implement. ANALYTICAL: Many commenters compare Hotwire to Phoenix LiveView (which uses websockets vs. Hotwire's HTTP-based approach), React/JSX, and Vue. Several note the cyclical nature of the trend ('everything old is new again'), pointing out that sending HTML fragments over AJAX was standard Rails practice 15 years ago. The COMET technique from 1996 is referenced as a precursor. A key architectural critique: 'you've got 2-3 frontends (web and cross-platform mobile)... RESTful APIs serving up JSON works for all 3... This however is totally web-specific — you'll end up building REST APIs and mobile apps anyways.'

No aggregate ratings were found for this product during the last harvest.