hallettj

Just a basic programmer living in California

  • 11 Posts
  • 173 Comments
Joined 11 months ago
cake
Cake day: February 23rd, 2024

help-circle


  • I’m sorry, I wasn’t completely clear. Yes you can run games on ARM on any OS with an emulator. When I said “won’t run any better” I meant you’ll get the same emulation slowdown on Linux as on Windows.

    The point of the article is that stuff runs faster on Linux because you don’t need an emulator, and it implies that that includes games. That’s disingenuous because any games that require emulation on Windows will also require emulation on Linux. If there’s no ARM build, there’s no ARM build.



  • It would be great if there were a way to translate x86 binaries for ARM without emulation. Has Valve found some way to do that? From a bit of searching I see they’ve been testing games on ARM, and that testing involves a version of Proton/Wine that runs on ARM. But it looks to me like they’re testing with ARM binaries for those games?

    I’m as enthusiastic as anyone about more Linux usage, and I agree that Linux support for ARM is a good selling point. But the reason Linux works so well on ARM is that we use all this open-source software that anyone can compile for ARM. I don’t think it’s honest to point to closed-source software that we can’t recompile, and imply that it will work better on Linux because other software runs natively on ARM on Linux.





  • You can do tag-based file management on Linux. Linux filesystems support “extended attributes” or “xattr”. There is some software out there that uses xattr for tagging. I don’t know what the best options are right now for tag-based file management, but I think it exists.

    Looking at what’s out there I see there are also apps that each use their own out-of-band tagging schemes. There’s a CLI, tmsu, and a GUI, TagSpaces. I don’t think these interoperate with each other’s tags.

    Of course those supplement instead of replacing hierarchical organization.

    The talk of hypertext and “escaping paper” makes me think of Obsidian which embraces hyperlinking, tags, and mind mapping via its canvas feature.


  • If the return type of a function is NonEmpty the value returned is guaranteed to be non-empty because it is not possible to construct an empty NonEmpty value. That’s the “make illegal states unrepresentable” mantra in action.

    At runtime you might get a list from an API response or something, and it might be empty. At that point you have a regular list. Following the advice from the article you want to parse that data to transform it into the types representing your legal states. So if the list is not supposed to be empty then somewhere you have a function that takes the possibly-empty list, and returns a value of type NonEmpty. But if the list actually is empty that function will fail so it has to be able to return or throw an error. The article uses the Maybe type for that which is one of the Haskell types for functions that can fail.

    Once you have parsed the input list, and successfully gotten a NonEmpty value the rest of your code can safely access the first element of the list because a value of that type is guaranteed to have at least one value.



  • Scotty: How do you think I wound up here? Had a little debate with my instructor on relativistic physics and how it pertains to subspace travel. He seemed to think that the range of transporting something like a… like a grapefruit was limited to about 100 miles. I told him that I could not only beam a grapefruit from one planet to the adjacent planet in the same system - which is easy, by the way - I could do it with a life form. So, I tested it out on Admiral Archer’s prized beagle.

    Kirk: Wait, I know that dog. What happened to it?

    Scotty: I’ll tell you when it reappears. Ahem. I don’t know, I do feel guilty about that.

    Scotty in the 2009 Star Trek movie explaining how he wound up in an especially remote posting.






  • hallettjtoLinux@lemmy.worldTips for kid workstations
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 month ago

    I set my kid up with Silverblue recently. After seeing it in use for a bit, as a power user I think it’s got some obnoxious compromises, and NixOS is a much better way to get the same benefits, and encourages safe experimentation at every level of the system. But for a beginner-friendly system that is very stable I think ostree distros like Silverblue make sense. Mostly stuff works fine, but you want to break out rpm-ostree occasionally to get a native package.

    I have another kid on Fedora as a control. So far things are fine. Previously I had both kids on Manjaro, but they weren’t able to keep up with upgrades long-term (over the course of a few years) without some intervention from me.

    Like I said in Silverblue stuff mostly works nicely:

    • Bottles running from Flatpak is running games in Battle.net without problems
    • Minecraft is running from the launcher installed from Flatpak
    • Roblox is running using Sober from Flatpak

    I think we may have installed steam natively using rpm-ostree. I think we ran into some sort of issue running Overwatch, and I quickly opted for the native steam package to get things working instead of trying to fix the issue using Flatseal. But I don’t remember what that issue was so I can’t say the Flatpack steam won’t just work for you. Maybe it was very slow Vulkan shader processing?

    My kid likes Minecraft mods so he needed java in his path to run installer jars. AFAICT in immutable distros the options for setting up CLI programs are either to run a different distro with native packages in a container (distrobox), or drop to rpm-ostree. I opted for the latter.

    On the hardware side I think one of the biggest factors in building a snappy system is choice of SSD. Like you said, spinning metal is out. But the idea that SSDs are all equal is a common misconception. The thing to do nowadays is to use an M.2 form factor which is where you get a little board that goes into a slot directly on the motherboard, sort of like a small, sideways RAM stick. That plugs directly into the PCIe bus which gives it tremendous bandwidth. Drives that support newer PCIe versions can be faster due to having access to more bandwidth, but the design of the drive itself is also a constraint.




  • Docker Compose runs services, manages dependencies between services, isolates each service in a container, manages a private network. Out-of-the-box flakes don’t do any of that - except arguably running one service at a time. What flakes do is build software, which is the thing that Docker Compose doesn’t really do. (Or doesn’t do well.)

    I’d compare flakes to Makefiles with waaay more expressiveness and reproducibility. Or maybe a comparison could be to a Dockerfile, minus containerization, with waaay more expressiveness and reproducibility.

    There are tools you can add on to get Nix to do what Docker Compose does:

    Arion is a Nix frontend for Docker Compose. You’re still using Docker Compose, but it layers on the extra expressiveness and reproducibility of Nix flakes, or other kinds of Nix expressions.

    process compose flake is similar, but instead of Docker Compose it is a frontend for Process Compose. You get a similar result, but without containerization. That can potentially avoid the need to run in a VM on non-Linux systems that don’t natively support containers.