Void is rolling release IIRC
That's what I thought, but the main website says Void focuses on stability over being cutting edge, which would imply some sort of release cycle. Or, maybe they just update packages less frequently.
I still hold Debian in higher regard since it's slightly easier for a novice to get used to
It's hard to beat Mint as a novice distro, for sure.
Did you look at Pelican?
I have not, but I will. I may also look at Zola, although it, too, appears at the surface level to be tightly coupled with markdown.
the template language is buggy and inscrutable
It's just Go templates, which are pretty solid; I'd be surprised by any bugs, unless they're in the Hugo short codes. The syntax is challenging, even if you're a Go developer and use it all the time. It's a bespoke DSL, and a pretty awful one: it's verbose, obtuse, and makes some common things hard.
Go is my language of choice, but my faith gets shaky whenever I have to use templates.
I'm not a huge fan of Python; despite its popularity, it's got a lot of problems, not least of which is the whole Python 2/3 fiasco; which, years later, is still plaguing us. However, if I can containerized it so it isn't constantly breaking in the background when I do a system update, I'm not opposed to using a project written in it. At least it isn't Node; I won't let that crap onto any server I admin.
Edit: Zola has the same problem as Hugo.
Ah, Ok.
I do as (or a similar workflow): I rsync the content directory and let Hugo on the server render. My sites are public, but perhaps they're just much smaller or not as popular; Hugo renders even my largest site in about a second, but for a large, slow, heavy-use production situation I could see a push-and-swap process for a more atomic site update.
I don't see the degradation you do, but there are so many possible variables.
My biggest gripe about Hugo is how limited it is in supporting source document formats. There's no mechanism for hooking in different formats, and the team is reluctant to merge PRs for other formats. When I started with Hugo, I had a large repository of essays spanning a decade and written in a variety of markup, from asciidoc (which I used for years), to reST, to markdown; and markdown is by far the worst. I was faced with converting everything to markdown, which was usually a lossy process because markdown is so limited, or not publishing all of that history. And now we have djot, which is almost the perfect plain text markup language, but I again have to first do a lossy conversion to markdown to get Hugo to consume it. It low-key sucks, and I'm actively looking for an alternative that has a more flexible AST-based model for which new formats can be added; something that consumes a format like pandoc's AST.
(I'm replying to you twice b/c totally different topics)
Tell me more about your Void experience. I've been meaning to give it a shot, except I don't get as much enjoyment out of fussing with distros as I used to. What are the pain points? Under Artix, I used dinit which I really liked, but I tried s6 first and absolutely hated it. I didn't try runit; how is it?
What I'm most interested in is xbps, because IMO it's the package manager that makes or breaks a system. I'm quite fond of pacman and have encountered far fewer dependency hell situations than I did with either rpm or deb, and rolling release is a must. xbps looks kind of like a rolling stable release?
I feel the same way about Artix. I had it on my laptop for a while, and it was a regular PITA. I think I may have made it harder on myself, because while getting rid of systemd was fine, I was also trying to do without NetworkManager and on a laptop that wasn't a great idea. I never did find a good, reliable set-up that managed access point hopping as well as nm.
Really, thinking back, Artix was fine; it really was just the roaming WiFi handling that gave me grief, and I did that to myself.
Ah. I was wondering where the "Hugo, but Rust" was.
I love these rewrites in other languages. They often learn from, and improve on, their predecessors in a way that having to maintain backwards compatability doesn't allow.
The screen shot is because they were proving a point.
Your other points are valid. Chrome? Logged in to Google? Google search?
Although, I will say that with as shitty as Google search has become, it returning the answer as the first result only underscores their point.
I had the similar comment about PKGBUILD/templates. The package definition is far less likely to do something malicious than the software you're installing; it's indeed a vector - a hypothetical AUR "git-plus" package could install git and a virus at the same time - but frankly I'm more concerned about upstream.
Are you running on btrfs? If not, why not? If so, install snapper and grub-snap or refind-btrfs, or whatever, and go wild.
Sounds like you might also be missing backups, but snapper you can have run every 10 minutes at almost no overhead. Then it won't matter if you delete something; you can always grab it out of a snapshot.
Yeah, there are a dozen "trash" commands. Honestly, I think changing muscle memory would be safer, but they could just install one of the trash commands and set up an alias as you say.
Mint eschews all of the Snap crap, though, doesn't it?
Jesus, please tell me it does. I've been recommending it to beginners. I thought it was sanitized.