31–40 of 94 posts
My feeling is that every serious programmer will end up inventing tools like this simply because the overhead of incorporating other people's tools eventually starts to overtake the overhead of maintaining one's own system.
I dare say it's how many currently-popular products came into being.
Earlier quoted context omitted.
Looks nice, Armin A question (that will surely become a FAQ) - how does this compare with Pelican? Is this a non-programmer-friendlier alternative to Pelican?
It is. But it also is a lot more flexible. It's more of a framework than a simple generator.
My feeling is that every serious programmer will end up inventing tools like this simply because the overhead of incorporating other people's tools eventually starts to overtake the overhead of maintaining one's own system.
Earlier quoted context omitted.
> the ini-file configuration seems a bit strange to me(esp since it seems to be ini-files that occasionally contain python code). Why did you go with them instead of making these python classes? To allow the GUI to edit parts of them as well? I grew to heavily dislike the idea of just executing random code to configure things. Impossible to expose to tools, even harder to reason about it. Note that these files do not…
>Lastly the reason ini over yaml is purely that this can preserve comments and doing the same for yaml is a lot more work i did not have time for :) Was that the only thing that bothered you about YAML/pyyaml or were there other things you'd like to see fixed?
From the original post: > There is very little innovation in that space and that's a bit unfortunate I'll have to respectfully disagree with Armin here, but perhaps I map the terrain a little differently than he does. In addition to the half-dozen tools he names, which are more narrowly targeted at blog-like static sites, the broader space of asset pipelines and static generation is seeing a lot of innovation. I'd po…
If you want to throw them into the same category, then sure, there is different stuff happening. But Gulp is even further away from something non programmers can use.
My feeling is that every serious programmer will end up inventing tools like this simply because the overhead of incorporating other people's tools eventually starts to overtake the overhead of maintaining one's own system.
Considering that one of the project's main goals is to address the needs of non-programmers, do you plan to add an improved Markdown editor (with some syntax highlighting and maybe buttons for things like titles, bold, etc.)?
From the original post: > There is very little innovation in that space and that's a bit unfortunate I'll have to respectfully disagree with Armin here, but perhaps I map the terrain a little differently than he does. In addition to the half-dozen tools he names, which are more narrowly targeted at blog-like static sites, the broader space of asset pipelines and static generation is seeing a lot of innovation. I'd po…
> I'd point to Gulp and Rails' latest as a sign that there's more work to do here. If you want to throw them into the same category, then sure, there is different stuff happening. But Gulp is even further away from something non programmers can use.
(And completely agree on the programmer-centric nature of these tools.)