[-] jplatte@discuss.tchncs.de 1 points 1 month ago

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").

[-] jplatte@discuss.tchncs.de 3 points 1 month ago

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.

[-] jplatte@discuss.tchncs.de 0 points 4 months ago

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).

[-] jplatte@discuss.tchncs.de 1 points 4 months ago* (last edited 4 months ago)

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

[-] jplatte@discuss.tchncs.de 2 points 7 months ago

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.

39
submitted 7 months ago by jplatte@discuss.tchncs.de to c/rust@lemmy.ml

I just released v0.1.0 of hinoki, my static site generator :)
The README.md should explain usage, and you can also see how I ported my blog to it here.

This project started because I'm not entirely happy with Zola, which does not support customizing page paths much (e.g. /year/month/day/title/index.html style paths) and made some other design decisions that I wanted to explore alternatives to.

You can download the binary from GitHub releases, or cargo install it from git.

Any feedback is appreciated, here or in the GitHub issues!

21
submitted 11 months ago by jplatte@discuss.tchncs.de to c/rust@lemmy.ml

jplatte

joined 1 year ago