| This claims to improve static websites by adding hot reloading, search, React, the NPM ecosystem, and faster page load. Search can already be done using Jekyll https://blog.algolia.com/instant-search-blog-documentation-j... (same idea of indexing at build time). Jekyll can hot reload with jekyll serve. Anyone who is familiar with React is familiar with HTML and CSS, whereas the opposite is not necessarily true. This means if you are able to use Phenomic, you are able to use Jekyll, but not vice versa. The NPM ecosystem is useful for authoring templates, not for the end user. If I were writing a Jekyll template I'd probably use webpack and npm, but I don't need that baked into the static site generator itself. Finally, page load is a really dubious claim, here's some numbers: On phenomic.io, the HTML for the index page weighs 3K gzipped (measured by copying HTML, removing what can be externalized and cached like styles + scripts, and gzipping index.html) When using Phemonic to do client-side loading, the JSON for the different pages is from 600B to 2.9K (as seen in network tools when clicking on the links in the top nav). A page load with phemonic therefore saves you:
* 2KB of bandwidth for some pages
* a few 302 not modified requests for static resources, which are negligible if you use HTTP/2 On the flip side of the coin, phemonic.js, the script bundle which makes all this magic possible, weighs 132KB, ie 44 times the size of the content the user wants to view. I can't see the value here. |