4 ms·

I know a lot of people that moved from Octopress to Hugo. I still keep using Pelican which has been around for close to a decade now and is still actively devel

I know a lot of people that moved from Octopress to Hugo. I still keep using Pelican which has been around for close to a decade now and is still actively developed.

capableweb 5y ago
Judging by the repositories Borkdude (author) is normally working on (seemingly), I'd say Golang (language Hugo uses) suffers the same problem as Ruby does. Seems anything Clojure is much better fit for them than anything Golang. Also, Hugo/Golang has it's own templating and really, who wants to deal with templating in 2021? XML/HTML as data (like Hiccup does) is so much easier and flexible.
- Kototama 5y ago
  In the case of Hugo one can download a binary release, so it does not suffer from the same problems.
  - capableweb 5y ago
    If you use Hugo for anything else than just basic blog posts, you're eventually gonna have to A) read the source to understand how stuff works and B) use their/Golangs horrible templating language. Using a binary doesn't make you avoid that.
    - Kototama 5y ago
      I once updated the dependencies of a octopress blog and it changed the enumeration rendering of lists from bullet points to numbers :-)
dsr_ 5y ago
I went through a phase of switching blog engines, then settled on Pelican. I haven't felt a need to switch for the last six years.
- rinze 5y ago
  Same here. Another advantage I've found is that I can have a virtualenv with my particular pelican version and never feel the need to update. There are no moving parts on the server, so as long as the HTML / RSS output works, everything is fine. At this point I don't like dealing with the (necessary, expected, I'm not critizising that) bits that break between versions.
auraham 5y ago
I use Pelican for my blog because it meets all my requirements: markdown, latex support, jupyter notebook support, syntax highlighting, and integration with GitLab. I tried another blog engines, like Jekyll and Hugo. However, since I do not use Ruby and Go daily, I did not use those engines. Some things I would like to see in Pelican are: - Better documentation in the code. The documentation for the final user is great. However, if you inspect the code, it will take some time to understand it since many functions are not documented. Compared to other code bases, like Keras, the docstrings can help the developer. - More themes. The default theme is not my favorite. Also, I think Jekyll and Hugo have better themes. (It is not a critic. I love Pelican)

I know a lot of people that moved from Octopress to Hugo. I still keep using Pelican which has been around for close to a decade now and is still actively developed.

capableweb 5y ago

Judging by the repositories Borkdude (author) is normally working on (seemingly), I'd say Golang (language Hugo uses) suffers the same problem as Ruby does. Seems anything Clojure is much better fit for them than anything Golang. Also, Hugo/Golang has it's own templating and really, who wants to deal with templating in 2021? XML/HTML as data (like Hiccup does) is so much easier and flexible.

Kototama 5y ago
In the case of Hugo one can download a binary release, so it does not suffer from the same problems.
- capableweb 5y ago
  If you use Hugo for anything else than just basic blog posts, you're eventually gonna have to A) read the source to understand how stuff works and B) use their/Golangs horrible templating language. Using a binary doesn't make you avoid that.
  - Kototama 5y ago
    I once updated the dependencies of a octopress blog and it changed the enumeration rendering of lists from bullet points to numbers :-)

dsr_ 5y ago

I went through a phase of switching blog engines, then settled on Pelican. I haven't felt a need to switch for the last six years.

rinze 5y ago
Same here. Another advantage I've found is that I can have a virtualenv with my particular pelican version and never feel the need to update. There are no moving parts on the server, so as long as the HTML / RSS output works, everything is fine. At this point I don't like dealing with the (necessary, expected, I'm not critizising that) bits that break between versions.

auraham 5y ago

I use Pelican for my blog because it meets all my requirements: markdown, latex support, jupyter notebook support, syntax highlighting, and integration with GitLab. I tried another blog engines, like Jekyll and Hugo. However, since I do not use Ruby and Go daily, I did not use those engines. Some things I would like to see in Pelican are: - Better documentation in the code. The documentation for the final user is great. However, if you inspect the code, it will take some time to understand it since many functions are not documented. Compared to other code bases, like Keras, the docstrings can help the developer. - More themes. The default theme is not my favorite. Also, I think Jekyll and Hugo have better themes. (It is not a critic. I love Pelican)