But the great benefit of returning to Server Side Rendering (SSR) is not needing APIs. Creating an API, whether REST or GraphQL, makes development slower. And it's not just Rails that is realizing this; Elixir with Liveview, PHP with Livewire, and even JS with HTMX, and React are following this trend. As Deno.js says: The Future (and the Past) of the Web is Server Side Rendering. - Source: dev.to / about 11 hours ago

I also needed to keep the infinite scroll on the homepage, authors, and categories pages which allow for scrolling all 200 posts as paginated pages of about 10 posts. To do so, I used partial HTML render routes that I render at build time with Astro (like any other page) and used HTMX to fetch pages on scroll. You can try it by scrolling on the blog homepage to see requests going out when scrolling to load the... - Source: dev.to / 1 day ago

I expect the author would mostly agree with you, but see the "motivation" header under https://htmx.org/. - Source: Hacker News / 7 days ago

A way less marketed version of this is htmx [1]. It is a single javascript file that enables this functionality. I mostly see people using it with Go backends but I think it is flexible. I have been meaning to try it out for a year or so. 1. https://htmx.org/. - Source: Hacker News / 14 days ago

Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq. - Source: dev.to / about 1 month ago

I try to avoid these tools wherever possible, given the choice I'd always go for tools like Blazer. https://github.com/ankane/blazer No such luck in my current role, Looker and PowerBI are both in use by different bits of the org and nobody has the ability to delve into the underlying figures. - Source: Hacker News / 4 months ago

As u/jaxn said you could use Blazer for this kind of thing. I would also look into materialized views or custom tables and a scheduled job that calculates the metrics they care about. That will take you a long way. Eventually you can use something like Metabase but I would put that off for as long as possible as it's really expensive and pretty involved. Source: 12 months ago

And it's Open Source: https://github.com/evidence-dev/evidence if you are into the Ruby on Rails world. It's super solid, and it's been an indispensable tool integrated to all my projects. - Source: Hacker News / about 1 year ago

I use Ahoy too, but I don't have very good visibility into the data. I should spend more time building queries and creating charts. I should probably set up blazer as well: https://github.com/ankane/blazer. - Source: Hacker News / almost 2 years ago

The Blazer gem provides a nice way to analyze the results easily. It is simple to install and allows SQL queries to run against tables. The query here shows that the candidate implementation is significantly faster than the original. - Source: dev.to / about 2 years ago