3 ms·
I recently upgraded my Jekyll install, and I must say this beast is becoming bloated. One of the many gem packages it now requires is a JS interpreter. Why?
by smutticus 12y ago
I recently upgraded my Jekyll install, and I must say this beast is becoming bloated. One of the many gem packages it now requires is a JS interpreter. Why?
I use an SSG because they're simple, don't require dynamic page loads and are more secure. However, the 'simple' part of this is wearing thin. Like so much of modern web software the developers only add things to it. They never remove or refactor. So you end up with massive dependencies and libraries from everywhere. It's crap software.
I still use it because I'm too busy to migrate to something else. Also, because I realize that whatever new tool I migrate to will eventually face the same fate. Eventually any compact SSG will eventually bloat just like Jekyll has. It's the nature of development these days.
- 0xdeadbeefbabe 12y agoWait, were there days when software bloat didn't happen? I think feature creep and accompanying bloat is human nature for all time.
- keithpeter 12y agoHummm, I used to use three bash scripts to publish the vanity site, now its two, I just 'curate' the list of pages by adding list items. Markdown -> script to generate a page with a header and footer and basic navigation. Another separate script to invoke lftp to sync with remote server when ready to publish. Lftp looks after incremental updating. In emergency, I can ssh into server and edit the html with nano. As I have shell access, I could just run the page generation script on the server I suppose.