Off-and-on trying out an account over at @[email protected] due to scraping bots bogging down lemmy.today to the point of near-unusability.

  • 10 Posts
  • 1.65K Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle


  • While I agree that I don’t think that an LLM is going to do the heavy lifting of making full use of Rust’s type system, I assume that Rust has some way of overriding type-induced checks. If your goal is just to get to a mechanically-equivalent-to-C++ Rust version, rather than making full use of its type system to try to make the code as correct as possible, you could maybe do that. It could provide the benefit of a starting place to start using the type system to do additional checks.


  • tal@lemmy.todaytolinuxmemes@lemmy.worldIt's really not that hard!
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 days ago

    Most of that is setting up third-party apt repos, which I don’t believe is necessary. Steam’s in the Debian trixie repo.

    https://packages.debian.org/stable/steam

    EDIT: I’d guess that the following would probably work on a Debian trixie system:

    If you have your system set up for only 64-bit packages, you’d need this at some point prior to the install, to let your system use 32-bit packages, since Steam’s only available as a 32-bit binary:

    $ sudo dpkg --add-architecture i386
    

    I think that deciding whether to use both 64-bit and 32-bit packages or not is an option in the Debian installer, but I might be misremembering.

    You can update your list of packages at this point, upgrade, all that, but that goes for any install operation; there’s nothing specific to Steam there. If you’ve just added 32-bit packages for the first time above, then you probably do want to update the list of packages, since your system won’t have a list of 32-bit packages yet.

    $ sudo apt update
    

    But then it’s just like any other installation of software.

    $ sudo apt install steam
    

    That actually just contains, as I recall, the Steam installer — enough to pull down and install the current Steam environment for a given user, which happens next time you run the Steam binary.

    $ steam
    

    EDIT2: I guess that assumes that you do have “contrib” enabled on the Debian repo, and I don’t know whether that’s enabled by default by the Debian installer or whether it’s an option during install or what. I do distinctly remember one point in time when “non-free-firmware” was not enabled by default, because I always had to turn it on to get support for <random hardware device with closed-source firmware blobs>, but I don’t know whether contrib is always enabled or not. I have main, contrib, non-free, and non-free-firmware enabled. From /etc/apt/sources.list.d/debian.sources:

    Types: deb deb-src
    URIs: http://mirror.i3d.net/debian/
    Suites: trixie
    Components: main contrib non-free non-free-firmware 
    Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
    





  • https://en.wikipedia.org/wiki/Zram

    One of the mechanisms for compressing memory in Linux. Trades CPU time for effectively having more RAM Recent versions of Fedora apparently have it on by default.

    I’ve read that zswap, another mechanism, is preferable on newer systems with NVMe/SSD, where paging isn’t as painful; that only compresses pages going to swap, but requires that you actually have some swap. I haven’t used either.

    Probably someone should try benchmarking them for various workloads if systems are going to be running on much less memory for a while. Was more of an edge case thing that not many people cared about, but if operating with less memory is suddenly more important, might have broader interest.

    On Linux, also possible to opt for lighter-on-memory versions of a lot of software that you’re kinda committing to using the Microsoft-provided version of on Windows. File browser, compositor, etc.