4 ms·

Even if the core project is feature complete and excellent, "death" can come from a lack of continued creation and maintenance of 3rd party integrations or plug

Even if the core project is feature complete and excellent, "death" can come from a lack of continued creation and maintenance of 3rd party integrations or plugins. Personally I found Jekyll plugins lacking and those that were good seemed pretty old/unmaintained. However I only moved to Hugo from Jekyll just because I didn't want to deal with Ruby gem installation and dependency management. I am not a Ruby dev by any means, I have enough dependency management misery from being a Python dev. Hugo installation is just a brew-installed or Go-installed CLI tool I never have to think about dependencies of, thanks to how great the Golang packaging/distribution situation is.

nirvdrum 5y ago
That's fair. Having to set up a Ruby installation to run a utility just isn't fun. Especially when the expectation is that you don't use the system-provided Ruby. You're supposed to go use a Ruby version manager and set all of that up. And that rough experience can contribute to its death, for sure. I just don't think "has few commits in the last month" is a great reason to declare a project as dead, especially one providing the backbone of GitHub Pages.
ryantgtg 5y ago
I recently went the other way - from hugo to jekyll - on a few sites. I find jekyll to be easier to install, modify, and maintain. And I recently rebuilt one of my Hugo sites the other day and got a notice about some function that is now deprecated and will break something soon. That’ll make the third time something like this has occurred with hugo in the last few years. Dun like it.
pmontra 5y ago
I'm using Jekyll (Ruby) in a docker container to manage the documentation of a Django project (Python). No need to deal with gems. Only docker pull and docker run. Most of the other developers don't know anything about Ruby. https://hub.docker.com/r/jekyll/jekyll/ https://hub.docker.com/r/jekyll/jekyll/

nirvdrum 5y ago

That's fair. Having to set up a Ruby installation to run a utility just isn't fun. Especially when the expectation is that you don't use the system-provided Ruby. You're supposed to go use a Ruby version manager and set all of that up. And that rough experience can contribute to its death, for sure. I just don't think "has few commits in the last month" is a great reason to declare a project as dead, especially one providing the backbone of GitHub Pages.

ryantgtg 5y ago

I recently went the other way - from hugo to jekyll - on a few sites. I find jekyll to be easier to install, modify, and maintain. And I recently rebuilt one of my Hugo sites the other day and got a notice about some function that is now deprecated and will break something soon. That’ll make the third time something like this has occurred with hugo in the last few years. Dun like it.

pmontra 5y ago

I'm using Jekyll (Ruby) in a docker container to manage the documentation of a Django project (Python). No need to deal with gems. Only docker pull and docker run. Most of the other developers don't know anything about Ruby. https://hub.docker.com/r/jekyll/jekyll/ https://hub.docker.com/r/jekyll/jekyll/