I interpret the groundswell interest in the SSG a testament the CMS does not address all the needs in the content publication pipeline. Some organizations have a focus on content creators. Others on developers. In general, the hacker mindset has an allergy towards ecosystems that remove control. The SSG is about providing a framework for the developer to assert control and regaining flexibility to deliver content independent of coding to a "system".

The CMS is a crutch. It has its place in certain organizations. But it is overkill for many use cases.

In truth, however, we shouldn't be pitting the SSG against the CMS. I believe the next leap of content creation is a mixture of both SSG and classical CMS. Check out the following links:

https://github.com/thyb/contentify https://www.contentful.com/ https://prismic.io/

There is a convergence about to happen between "dynamic" content and the SSG. It could be called CMS as an API.