Live data from Hacker News

Ivy: a minimalist static site generator in Python

github.com

41–50 of 58 posts

Re: Ivy: a minimalist static site generator in Python

#42
post #35

Earlier quoted context omitted.

Apache Ivy has been effectively a dead project for years; I'm fine with letting someone else have a turn using the name.

https://github.com/apache/ant-ivy/commits/master doesn't look very dead to me.

What do you know, someone's actually working on it now!

Last time I checked (a few months ago), the project had gone about 2.5 years with no releases, no public mailing list activity, and almost no non-trivial source code commits. Bug reports, whether trivial or show-stopping, were consistently ignored, e.g. https://issues.apache.org/jira/browse/IVY-1485

It looks like some of the Ant contributors finally got around to picking up the project again a couple months ago. Here's hoping that they can get things back on track.

Re: Ivy: a minimalist static site generator in Python

#43
post #34

Earlier quoted context omitted.

OK - Serious questions for things I've done in Pelican: 1. Can I get Jekyll to use Org files without writing any Ruby code? 2. Can I get Jekyll to handle math using MathJax without writing any Ruby code? 3. Can I get a "next article for a given tag" in Jekyll without writing any Ruby code? (What I essentially need: A post usually has "next" and "previous" article links. I want a "next" and "previous" article for ever…

I believe you can do 3, but it would take a non trivial amount of work to do so.

It requires writing a plugin for Pelican too, but I was a little irritated with the claim that Jekyll will do whatever you want without needing to write Ruby.

Re: Ivy: a minimalist static site generator in Python

#44

This is public domain, which is very generous, but apparently problematic. E.g. see comments here https://www.red-gate.com/simple-talk/opinion/geek-of-the-wee... : "If I had known as much about copyright in 2001 as I know now, I probably would have gone with something like the Apache license. Live and learn…"

It's really only problematic if you want businesses to use it. They don't just want the right to use it, they want to be given permission explicitly. One reason is that public domain is not recognized everywhere. It's unlikely a static site generator needs to worry about being public domain.

Re: Ivy: a minimalist static site generator in Python

#45

For a minimalist static site generator, I think it's hard to beat just writing your own that does exactly what you want and nothing else. In a hundred lines or less of Python, you can have your minimal generator, know exactly how it works and how to extend it, and be able to refresh your memory on conventions/configuration with thirty seconds of scrolling through the source.

I've found that for static html it's easiest to put all the files into one directory, manually create an index file, and copy a five-line Makefile into the directory that compiles everything to html using Pandoc. I wasted too much time using something written the way others wanted it. When I wanted to change something, I'd be digging through bad documentation (if it was documented at all). I'd have to remember a gazillion different configuration options. Sometimes automation makes things worse, because you'll never use most of the options, yet they get in your way, and it's at best just good enough, never the way you want.

Re: Ivy: a minimalist static site generator in Python

#46

This is public domain, which is very generous, but apparently problematic. E.g. see comments here https://www.red-gate.com/simple-talk/opinion/geek-of-the-wee... : "If I had known as much about copyright in 2001 as I know now, I probably would have gone with something like the Apache license. Live and learn…"

It's really only problematic if you want businesses to use it. They don't just want the right to use it, they want to be given permission explicitly. One reason is that public domain is not recognized everywhere. It's unlikely a static site generator needs to worry about being public domain.

I wonder how do businesses make do with SQLite's public domain license. I see it used everywhere.

Re: Ivy: a minimalist static site generator in Python

#47
post #46

Earlier quoted context omitted.

It's really only problematic if you want businesses to use it. They don't just want the right to use it, they want to be given permission explicitly. One reason is that public domain is not recognized everywhere. It's unlikely a static site generator needs to worry about being public domain.

I wonder how do businesses make do with SQLite's public domain license. I see it used everywhere.

They can buy an alternative licensed version from Richard Hipp if they're worried about it.

Re: Ivy: a minimalist static site generator in Python

#48

Ivy looks great. That said, every time I see a new SSG in Python, I get all excited about it for a minute. Then I remember this bit of advice: "Just use Jekyll". > Jekyll is not better than the rest for any fundamental design reason; it’s better because it’s enormously popular and therefore excels in the long tail of details. > ... > If, like me, you secretly believe that everything is better if it’s written in Pytho…

I think Hugo is popular enough these days for that argument to apply to it. It's far easier to get up and running, too.

Agree. I haven't tried many alternatives, but had a need for a quick website recently and Hugo was exceedingly easy to use and has a lot of nice looking themes.

Re: Ivy: a minimalist static site generator in Python

#49
No disrespect, but, seriously, given that project was created 9 months ago, "minimalistic static site generator" isn't really sufficient project description, let alone marketing slogan. What I want to know is why to use it over

* Jekyll

* Hakyll

* Hugo

* Pelican

* Sculpin

* ...

Post reply on HN