Hey, you probably know about restic and borg for backups. They are pretty mature and very commonly used.

Rustic is a fully compatible reimplementation of restic in Rust and they do seem to have implemented a few improvements over restic. The developer even used to be a contributor on restic.

Is anyone here using it already? It looks super promising but I’d love to hear your opinion!

  • Nine
    link
    English
    181 year ago

    What is the advantage of using this over restic?

      • @[email protected]
        link
        fedilink
        English
        51 year ago

        It sounds like they have some nice improvements, but I wonder why they didn’t contribute them back to the original restic project.

        I also wouldn’t rely on an immature piece of software to handle backups - you want to avoid as many risk factors as possible with backups, since when you need to restore you really need it to work.

      • BlackEco
        link
        fedilink
        English
        3
        edit-2
        1 year ago

        FYI, you formated your link wrong, it should be [here](https://github.com/rustic-rs/rustic/blob/main/docs/comparison-restic.md)

        • @saddlebag
          link
          English
          21 year ago

          I can never remember the order and I’m using Wefwef which doesn’t offer markdown insert. Thanks :)

          • @418teapot
            link
            English
            51 year ago

            The way I remember the order is that the parentheses around the link would make grammatical sense outside of markdown (the goal of markdown is to still be fully readable even when looking at the raw source).

            For example if I were posting on a forum that didn’t have markdown support which one of these would make more sense:

            1. You can find that on this lemmy instance (https://lemmy.world).
            2. You can find that on (this lemmy instance) https://lemmy.world.

            Option 2 makes no sense grammatically. Then you just need to use the square brackets (which rarely show up in non-markdown text) to denote the link range.


            Alternatively, if you still have a hard time remembering the order, you can use reference-style links which make it even more readable outside of markdown rendered contexts (note that there are no parentheses in this version, nothing to get confused):

            [Here is a link][1] and [here is another link][2].
            
            [1]: http://example.org
            [2]: http://example.com
            
    • @[email protected]
      link
      fedilink
      English
      -61 year ago

      Looks like the rust-cult is at it again rewriting existing stuff for no gain but pushing rust on others.

      • @[email protected]
        link
        fedilink
        English
        16
        edit-2
        1 year ago

        A lot of the time, rust rewrites are more for devs, than users. Rust code is just easier to maintain (in the long-run 😉) and harder to make buggy. But some times the apps do just run faster when compiled with Rust.

        • @[email protected]
          link
          fedilink
          English
          31 year ago

          Is it that much better than Go? Seems like the original restic was written in Go which afaik is pretty similar performance and syntax wise.

          • @[email protected]
            link
            fedilink
            English
            81 year ago

            Go has its fair share of design problems and is not as memory efficient due to its garbage collector. Also it will probably always be linked to Google in some way.

      • Celediel
        link
        fedilink
        English
        51 year ago

        Use fd instead of find, or rg instead of grep and tell me there’s no gain. The speed increase alone is astounding, and beyond worth it.

        • @[email protected]
          link
          fedilink
          English
          41 year ago

          Oh shit, will definitely be trying this out. I tend to make wildly overzealous find searches