When comparing Octopress vs JBake, the Slant community recommends Octopress for most people. In the question“What are the best static site generators?” Octopress is ranked 4th while JBake is ranked 26th. The most important reason people chose Octopress is:
Octopress is designed to remove all the time-consuming and frustrating tasks you usually have to deal with when using Jekyll. You don't have to write your own HTML templates or do any configuration to get started. The default template also takes care of any basic CSS/JS you need to write to get going.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very easy to use
Octopress is designed to remove all the time-consuming and frustrating tasks you usually have to deal with when using Jekyll. You don't have to write your own HTML templates or do any configuration to get started. The default template also takes care of any basic CSS/JS you need to write to get going.
Pro Lots of plugins (from Jekyll + 3rd party)
Another advantage of being based on Jekyll is default access to the extensive plugin system for Jekyll. There are also plugins developed specifically for Octopress.
Pro Based on Jekyll
As Octopress is simply a framework on top of Jekyll, it benefits from being based on one of the most popular site generators available. The primary benefit is that it is backed by git and is built in such a way that the site can be easily re-generated if the content changes.
Pro Uses Markdown for writing
Uses the Markdown syntax for writing blogs.
Pro Server included
Localhost server is included and can be used to preview content during editing process.
Pro Blog Aware
RSS feed, archive and tag support. Posts/Topics are a first-class citizen in jbake.
Pro Runs on / Control from the JVM
The site generator is just a specific usage of the JBake Java API. As such, jbake is easily integrated into other JVM software.
Pro Typical inputs
Markdown, asciidoc, plain HTML is supported
Pro Open Source (MIT License)
boosts permissive MIT License.
Cons
Con Not Actively Developed
Last commit is Feb 22, 2016, Social media hasn't been updated. Dead project?
Con Inefficient
Adding a new post, for example, causes the entire blog to be regenerated.
Con Some plugins have hard-coded values
Con Not as flexible as Jekyll
Con Code and data are intertwined
Con Runs on the JVM
JVM is a double-edged sword (startup time, memory usage, CPU overhead, ...) which might be considered overkill for a static site generator.