Because when you release a blog post, you set the publish date to when you started writing, rather than the day it goes out? What?

“This guy” that Phoronix “called out” isn’t even who wrote the blog post you’re commenting on.

FWIW, the last breaking release of axum before this came out in Nov 2023.

I would also argue that the vast majority of axum tutorials still “work” - your app would panic at startup if using the old path capture syntax with a note that the syntax changed which should immediately get you back on track, and I wouldn’t expect the other features that were changed in a breaking manner to be used in tutorials much.

Ah yeah, we recently removed that example because it was kind of hard to upgrade in a nice way. One could likely take the example from the PR branch here and submit it to tonic instead. I think they might have a bigger interest in having it.

Same situation here :D

Were you also blocked by opentelemetry?

Yeah, I agree. I don’t post so often so I forget. Added now.

Hey, only saw this now! Have you investigated some of the options already now?

Re. Jekyll, I have the same experience which is what got me to try Zola. I find it rather nice to use at least when you’re okay with its limitations – which hasn’t always been the case… missing flexibility for output paths has been an annoyance. What really led me to make my own Rust SSG instead of forking Zola is that I found Zola to be quite hard to hack on, and Tera (its templating lang) to be a little buggy / much less elegant than minijinja API-wise.

Re. link checking, have you seen lychee? When I found out about it, the priority of building my own link checker in my SSG (that was only an idea at that point, I think) basically dropped to zero :D

Zola supports this? I’ve never heard of it and can’t find anything about it in the docs. I’d be interested to find out how it’s implemented there, but it does seem a bit too complex for my liking on first thought.