• 7 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: February 1st, 2023

help-circle
rss
  • AI has a lot of great uses, and a lot of stupid smoke and mirrors uses. For example, text to speech and live captioning or transcription are useful.

    “Hypothetical AI desktop” “Siri” “copilot+” and other assistants are smoke and mirrors. Mainly because they don’t work. But if they did, they would be unreliable (because ai is unreliable) and would have to be limited to not cause issues. And so they would not be useful.

    Plus, on Linux they would be especially unusefull, because there’s a million ways to do different things, and a million different setups. What if you asked the ai “change the screen resolution” and it started editing some gnome files while you are on KDE, or if it started mangling your xorg.conf because it’s heavily customized.

    Plus, every openai stuff you are seeing this days doesn’t really work because it’s clever, it works because it’s huge. Chatgpt needs to be trained for days of week on specialized hardware, who’s gonna pay for all that in the open source community?


  • Distributing software is not instantaneous. Assuming that Mozilla has already sent the update to flathub, it will take some time before it’s validated and available for download.

    If instead of flatpak you had used native packages, you would be in the same situation, as fedora’s update system keeps updates in testing until enough people say it’s fine.

    If you wanted to get the update as soon as possible, you would have to download the prebuilt binary from Mozilla, but then you would have to update manually and everything.

    Just be patient for a few days.





  • IMHO I would avoid the ublue distros and just go for official fedora spins. The guys have good intentions, but they don’t have the means to maintain that many distros “properly”. I often end up enabling copr packages for bazzite in my fedora install, just to find out the program doesn’t work.

    That being said, as the other comments told you, you can still install native apps on immutable distros, it’s just a bit more work. I don’t expect distrobox or toolbox to be much faster than flatpak, as they are all just containers with a nice cli, except flatpak is easier to update. But trying costs nothing







  • It’s a supermicro x8dal-i with two xeon x5650 from 2010. 6c/12t each, base frequency 2.33 GHz, turbo to 3.2 GHz single core, 3 DDR3 ports each in two Numa nodes, for a total of 24GB at 2400 MT/s. It only supports PCIe 2.0, for a 1060 3GB.

    It’s slow as hell in single thread, it’s acceptable in multi thread. It doesn’t go out of memory. It sounds like a lawnmower. It boots up between 1 min and 6 min. It overheats and shuts down in summer (hence the desk fan and the little fan blowing on the chipset). It chokes that 1060 with its slow PCIe. Lots of sata, only one 128 GB SSD. Most games from before the 2021 run. Overall pretty cool. It has two Intel gigabit Ethernet.

    Both windows 10 and Ubuntu are taking a toll on it. But I bet a nice fresh install will fix it. But I won’t do it because it’s not my main kick anymore




  • I think you are confusing “windows like” with “user-friendly”. A “bespoke archive, that you find on some developer’s website, that you extract and somewhere it contains an executable and assets, that you move where you want to keep them, and then the user remembers to manually update it sometimes somehow” is not how you usually do stuff on Linux and is not even user-friendly.

    Distributions come with programs like “gnome software” or “kde discover” that allows the user to graphically install programs from the distro’s package manager, or from flatpak or snap. It will also help them to keep them updated and to manage dependencies. That is user-friendly.

    I suggest using flatpak. It will work on almost all distros out of the box and will be easy to install and maintain for the user. If flatpak is too “bloated” for you because it uses containers, then you need to package it for every distro manually, but that’s a lot of work. If it’s something that just needs to be used once and never again, consider an appimage or a script, because they don’t need to be installed.

    Distros are different operating systems, it’s not gonna be easy to package for all of them without compromises.

    Also, if you really really really need to use your bespoke archive, you can do like native steam games do, and put every library you link in the archive, and link with relative paths instead of system wide paths, or with a launch script that loads your provided libraries. But that’s not a great user experience. Steam gets away with it because it’s the launcher that manages the whole thing.





  • You are not supposed to power the GPU like that. You should use two separate cables from the supply. The other connector of the same cable is intended to “daisy chain” low power cards.

    It will probably work anyway, but better safe than sorry.

    Edit: I think it’s needed because:

    1. The power supply might have separate circuits for separate cables and might not be able to supply all the power needed by the GPU through just one
    2. The cable might not be rated to have that much power flow through and might overheat and melt over time
    3. If you could just fork the cable into two why would they put two connectors on the GPU, it’s not like they have different voltages, they are literally daisy chained