5 ms·

Use any SSG not written in javascript and you'll be fine. Hugo, Zola, Jekyll, etc. Though if I was starting from scratch I might avoid Jekyll just because of th

Use any SSG not written in javascript and you'll be fine. Hugo, Zola, Jekyll, etc. Though if I was starting from scratch I might avoid Jekyll just because of the Ruby dependency.

root_axis 4y ago
> Use any SSG not written in javascript and you'll be fine. Commonly stated but not actually true. For example: https://github.com/getzola/zola/blob/master/Cargo.lock https://github.com/getzola/zola/blob/master/Cargo.lock https://github.com/gohugoio/hugo https://github.com/gohugoio/hugo (scroll to the bottom of the README)
- weego 4y ago
  To be fair in every day use Hugo is a single very portable binary
  - procombo 4y ago
    This. Makes everything so smooth. Serverless cloud providers love it too. (Cloudflare Pages, etc.)
- skrtskrt 4y ago
  Yeah Hugo has the advantage that dep management for Go is 10000x simpler than JS, Ruby, Python, etc., particularly when you are someone who doesn't work in that language regularly. Plus as sibling comment says you usually don't do anything but install hugo, `hugo [command]`
- IceWreck 4y ago
  You don't need these deps to install it, just to compile it.
- game-of-throws 4y ago
  If that scares you, you must be terrified of modern Linux distros.
gglitch 4y ago
Honest q: what’s the problem with Ruby? Compile time? Gem management? I’m using Jekyll and sometimes wonder if I’m missing anything from the newer systems. My compile time is negligible, and once I figured out how to integrate Tailwind, I’ve had no issues.
- salmo 4y ago
  I’ve used Sphinx, mkdocs, Jekyll, and Hugo. I don’t see a reason to switch a site from one to the other if you and any collaborators are comfortable maintaining the runtime. The same goes for JS based tooling (I imagine), I just don’t node so good. Personally, I use Hugo for new projects because it lowers the burden for content collaboration. Templating is weird in Go, though if you’re working on themes. I like it now, but it’s procedural vertically and LISPish horizontally, if that makes any sense. Usually it’s just me or me and another guy messing with that, and others often unfamiliar with anything except Java contributing vanilla markdown documentation. “Clone the repo, run this binary” is helpful there.
- game-of-throws 4y ago
  Personal preference mostly. rvm/gem/bundle is just a lot to set up and keep in your head compared to running a statically-linked binary. It feels like a relic of a previous era. Plus compiled languages are faster, and massively easier to set up if you have contributors running Windows. But like sibling said, if you're happy with your setup, keep it.

Use any SSG not written in javascript and you'll be fine. Hugo, Zola, Jekyll, etc. Though if I was starting from scratch I might avoid Jekyll just because of the Ruby dependency.

root_axis 4y ago

> Use any SSG not written in javascript and you'll be fine. Commonly stated but not actually true. For example: https://github.com/getzola/zola/blob/master/Cargo.lock https://github.com/getzola/zola/blob/master/Cargo.lock https://github.com/gohugoio/hugo https://github.com/gohugoio/hugo (scroll to the bottom of the README)

weego 4y ago
To be fair in every day use Hugo is a single very portable binary
- procombo 4y ago
  This. Makes everything so smooth. Serverless cloud providers love it too. (Cloudflare Pages, etc.)
skrtskrt 4y ago
Yeah Hugo has the advantage that dep management for Go is 10000x simpler than JS, Ruby, Python, etc., particularly when you are someone who doesn't work in that language regularly. Plus as sibling comment says you usually don't do anything but install hugo, `hugo [command]`
IceWreck 4y ago
You don't need these deps to install it, just to compile it.
game-of-throws 4y ago
If that scares you, you must be terrified of modern Linux distros.

gglitch 4y ago

Honest q: what’s the problem with Ruby? Compile time? Gem management? I’m using Jekyll and sometimes wonder if I’m missing anything from the newer systems. My compile time is negligible, and once I figured out how to integrate Tailwind, I’ve had no issues.

salmo 4y ago
I’ve used Sphinx, mkdocs, Jekyll, and Hugo. I don’t see a reason to switch a site from one to the other if you and any collaborators are comfortable maintaining the runtime. The same goes for JS based tooling (I imagine), I just don’t node so good. Personally, I use Hugo for new projects because it lowers the burden for content collaboration. Templating is weird in Go, though if you’re working on themes. I like it now, but it’s procedural vertically and LISPish horizontally, if that makes any sense. Usually it’s just me or me and another guy messing with that, and others often unfamiliar with anything except Java contributing vanilla markdown documentation. “Clone the repo, run this binary” is helpful there.
game-of-throws 4y ago
Personal preference mostly. rvm/gem/bundle is just a lot to set up and keep in your head compared to running a statically-linked binary. It feels like a relic of a previous era. Plus compiled languages are faster, and massively easier to set up if you have contributors running Windows. But like sibling said, if you're happy with your setup, keep it.