• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • I gotcha:

    • Btrfs
      • BTree File System
        • A Copy on White file system that supports snapshots, supported mostly by
    • ZFS
      • Zetabyte File System
        • Copy on Write File System. Less flexible than BTRFS but generally more robust and stable. Better compression in my experience than BTRFS. Out of Kernel Linux support and native FreeBSD.
    • HFS+
      • what Mac uses, I have no clue about this. some Copy on Write stuff.
    • NTFS
      • Windows File System
      • From what I know, no compression or COW
      • In my experience less stable than ext4/ZFS but maybe it’s better nowadays.




  • It’s not too bad. I very rarely recompile everything from scratch and after I do that I just create a snapshot with btrfs. Are usually then chroot into that snapshot and compile everything natively overnight for that 5% Theoretical performance boost.

    Most recently I took that snapshot and then used btrfs send to adapt it to a laptop as well and that worked quite well actually.

    Everything I install is typically through flatpack or distro box just like silver blue. This means install times are pretty much okay but I have a huge amount of flexibility in the way the system works

    Also heaps of binary packages as well, so that’s not too bad. The binary packages much slower than both arch and Alpine but not a lot slower than for example Fedora.


  • Hawk@lemmynsfw.comtoSelfhosted@lemmy.worldDocker or podman?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    4 months ago

    They both kind of suck in their own way.

    If you want to things to run at startup and you’re not on systemd, rootless docker is probably easier.

    Otherwise podman is mostly fine but be careful of native overlay if you’re not on BTRFS, this causes some pretty long build times.








  • Simply, the lsp is far less useful. An object might have a dozen methods that act like verbs or some attributes that act as adjectives.

    In Julia there is a huge number of functions, that work differently for different types and different combinations of types. So finding the documentation involves finding the right name for a function that does different things for different types, then scrolling down the docs for the the behaviour that corresponds to the specific combination of inputs.

    I moved from R/Py to Julia for a while before moving back to Py (and a little bit of Rust).

    I love how fast Julia is and the 1-index is fine for me, but I still prefer py for the oop.