I&#x27;m still struggling to get on board with this. It seems to just favor speed above all else. I found the linked article  at <a href="http:&#x2F;&#x2F;www.smashingmagazine.com&#x2F;2015&#x2F;11&#x2F;modern-static-website-generators-next-big-thing&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.smashingmagazine.com&#x2F;2015&#x2F;11&#x2F;modern-static-websit...</a> to be a bit more helpful in pitching the case, but even so it seems like just pulling the complexity of dynamic sites into the build stage of the static ones all because writing efficient DB queries is &quot;hard&quot;. For a companies front page, I can see the benefit of generating content once instead of for every client, but what happens when you need to present information beyond the generic? What happens when you need to show a user&#x27;s order history? Let them change their password? Allow them to see the distance of that run?<p>I feel old and crotchety, but I just find it a bit strange that as we get more and more obsessed with data, this emerges; something that seems less that optimal for dealing with it. They make the comparison themselves, but it seems like reverting from &quot;Web Applications&quot; back to &quot;Web Sites&quot; and just filling it with API calls to actual Web Apps.