3 ms·
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 c
by 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 agoI’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 agoPersonal 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.