My blog has 512 posts since November of 2002. The only way using a static page generator is at all feasible to me is by not having to regenerate the site on my end.
Two reasons for this: One is that the page generation takes up to 45 seconds (with Jekyll, so punch might be faster there). The other is that if I generate locally and then want to push to github pages (having *.github.com is very fitting for a programmer's blog IMHO), every post will also create huge amounts of additional changes (I have a "recent posts" section in the sidebar) which makes for a really, really messy commit history.
So with Jekyll (based on jekyll-bootstrap), I can create a small commit for a new post and then offload page generation to github, fixing both of my issues.
As such for $other_solution to really be better than Jekyll in my use case, it must at least have that one feature that is page-generation by github pages.
Punch doesn't have it and thus, I wouldn't say that it's "better than Jekyll".
I have built a project (http://substancehq.com/) which is like jekyll in the way that it provides you with a configurable layout, And being a hosted app, I regenerate only the content which has changed. I have used jekyll for more than 2 years now, but the minor editing stuff was the last straw. With jekyll when you edit minor things because you don't have the right markdown syntax you have to redo the git commit -> git push steps.
This is a great start. Jekyll is perfect for blogs, but as the readme says this is for full websites. I just don't understand why I would want client-side rendering- isn't the entire point of Jekyll that you would serve static files?