• 1 Post
  • 46 Comments
Joined 2 years ago
cake
Cake day: August 10th, 2023

help-circle
  • Alright, this is gonna be long.

    Firstly, yes, different static site generators have different templating langauges. But just like normal programming languages, it is easy to transition from one templating langauge to another. If you take a look at the syntax:

    Not drastically different, but reading the docs, they are all similar enough, and easy to learn.

    I wouldn’t call go’s templating language “esoteric”, but it should be noted that jinja2 is has other uses, most notably it is the templating engine that Ansible uses.

    As for the docs… This could probably be a blog post by itself.

    Firstly, take a look at this website: https://killedbygoogle.com/ . Google has created and then killed 296 projects, many of which were actively used and working. Why?

    This is because, internally at Google, you get promoted if you either A: write software, or B: add more features to software. So what happens is people write software, get promoted, and then realize they don’t get paid more if they actually maintain that software, so they just kill it. Also, they forget to write documentation (because it doesn’t pay more or get you promoted).

    Hugo, is by a Google Engineer, and it shows (or at least, it used to). Software by Google has two distinct characteristics (actually 3 if we count being written in Go).

    • It has every feature you could ever want, even stuff you haven’t heard of
    • And it’s poorly documented. Or not at all lmao.

    But, “being poorly documented” is not a permanent fixture of this software, but instead something that mostly persists for as long as it’s Google software. Often, these projects get “adopted” by the wider community, who fixes up their documentation. Looking at hugo’s docs, it doesn’t seem be nightmarishly bad, especially for the core, main set of features. Like the setup docs appear to be clear (although a more complex process than alternatives).

    But like, for search options: https://gohugo.io/tools/search/ . That google software pattern continues. There are like 10 options on the page, and no docs from hugo on their usage/installation lol.

    Anyway, I would recommend eithier Pelican or Jekyll, given your requirements. Because everything you write is in markdown, it will be fairly easy to move from one static site generator to another, even if you are dissatisfied.

    Also, kinda sorta relevant:

    (source)

    But the point I’m trying to make is the same. Don’t agonize over selecting the perfect static site generator.



  • It’s actually not that hard. (Well it is, media and networking are hard, but)

    I think the problem is that when people search for something better than Teams (or any other software), they confuse “better than”, with a mostly nonexistent “best”. In doing so, they skip over the way every single thing people suggest is “good enough”.

    Like, following this thread, we went from “I want a teams (voice/video/chat) alternative” to “Yeah I don’t like Jami because it leaks metadata.” How did we go from wanting a teams alternative, to wanting privacy with no metadata leakage? Those are very different things, and you make tradeoffs if you take one set of feature over the other. If you just add “no metadata leakage” on top of your current wishes, then you are probably going to be disatisfied with every option given.

    Or “Firewalls and hole punching!” (implying a p2p architecture) and “depends on peers being reliable” (being frustrated with the pitfalls of a p2p architecture). Again, wtf? Of course there is software that is both p2p and client server, but that is hard and tradeoffs will end up being made, even purely in what the developer spends their limited time on.

    This person just needs to get out of their head, whip up deployments for every software (or suite if there is more than one) mentioned in the thread, and pick the one that looks the nicest.


















  • I’m pretty sure it’s possible to use timeshift to create backups on another drive using rsync (instead of btrfs). They are incremental, and deduplicated, as well.

    But the other commenters are correct, timeshift is not a backup tool, it’s more for snapshots to undo system changes you may not want. In addition to that, it doesn’t do user files by default — because again, it’s not a backup tool.

    btrfs send/receive technically does what you want, using btrfs to do backups to another drive, but I don’t think any GUI app supports it. Plus, you would have to create snapshots for btrfs from the command line.

    Your best bet are apps explicitly designed for this usecase, like someone mentioned pika, or borg or restic are good choices. They don’t do BTRFS, but they do incremental, deduplicated updates in a user friendly way.