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.
We've been doing this for a few years too! However, the plants we have are not super well suited for it ^^
I love the second picture.. We have a very similar plant with very thick stalks in the attic now and are moving soon, maybe should have it in the living room in the new place for decorating!
How do you clean them? For the MX master, the worst bit to me is the rubber inside the scroll wheel(s).
Re. breakage, one was almost certainly my own fault with transporting it too much / carelessly (primary scroll wheel could no longer enter the "clicky" mode), though I've also had the sensor for mouse movement fail on another one (those two are the ones I recently "merged").
I've owned three or four MX Master mice. That statement alone should show pretty clearly that it's not a "buy it for live" device. I did manage to merge two broken ones into a working one recently, but I don't expect it to survive another 10 years.
One of the major problems even if nothing technically breaks is the rubber coating getting greasy or sticky with time. This rubber coating is unfortunately also used in other logitech mice, especially the more expensive ones.
EDIT: Here’s a screenshot of what I mean by saying I’ve gone way overboard.
Wow! Impressive :)
You accidentally re-used the link to the Zola issue tracker there.
Oops, fixed.
it’ll depend on how amenable it is to checking a site rooted in a
file://URL so I don’t need the overhead and complexity of spinning up an HTTP server to check for broken links.
Wouldn't you want your SSG to include a dev-server anyways? Zola has zola serve which even does incremental rebuilds, but something less sophisticated should be easy to add to your own (only took me a weekend to add to hinoki including rebuilds, though mostly starting the build from scratch on changes).
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
the
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.
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.