• 24 Posts
  • 619 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle


  • In short, X11 is a bit unsecure in its concept (like every program can read keyboard inputs you are doing right now). The multi monitor configuration possibilities and mixing different setups is basically impossible (I mean stuff like mixing 4k@120 Hz with G-Sync and another one with 1080p@60 Hz with just V-Sync). X11 or XOrg has a long history since the 80s with many versions, the code base is spaghetti code and its not a pleasure for developers to work on.

    Wayland is new, with a fresh and modern code base. It eliminates the security and monitor issues. Programs not written for Wayland does not work, but luckily there is XWayland, which allows running X11 games on Wayland. You can think of like Proton for X11, but without the benefits of Wayland, just a compatibility mode. In Wayland there are sub protocols, meaning standard definitions, that are developed and added after some time passes. I personally think protocols being like an addon that allows doing more stuff in a standardized way across all systems that support it. Developers in Wayland have a much better time working with its modern code base.

    Have a look at https://wayland.freedesktop.org/docs/html/ch03.html .


  • Firefox Translations now supports more languages than ever! Pages in Simplified Chinese, Japanese, and Korean can now be translated and Russian is now available as a target language for translating into.

    Oh finally support for these Chinese, Japanese and Korean! Less reason to use Google translate. Edit: Just tested it on two websites, oh my goodness, it works well!













  • Basically an distribution that is not a rolling release. Its hard to recommend a specific distribution. You could use one of the Ubuntus, a Fedora Atomic variant, Mint, they should be able to run for weeks without issues. Unless you update a system component that requires a restart to take into effect. Why not openSUSE Leap?

    I’m personally on EndeavourOS, a rolling release and update often (even the Kernel). My PC is also on for 24h, usually for days, sometime even a week. One trick to avoid some of the restarts is to just logout and login the user. This should be no problem for you and at least some of the components start fresh due to login.




  • Thanks for posting. I find the echo part and extra use of variable is a little bit flaky. Here is a modified version. But I am not 100% sure if its doing what your script is doing.

    I skipped the extra variable and echo and grep, by comparing its content with ${*}, which is similar to ${@}, but won’t separate each argument and create a single string instead. The =~ /$ is a regex comparison, which Bash supports native. Then I am using ${@} for the call, which separates each argument. Maybe this could be done with ${*} instead. I’m not sure which of them is the correct one for this case. At least it seems filenames with spaces work. Otherwise, not claiming it would be better. Just giving some food for thoughts.

    #!/usr/bin/bash
    
    if [[ "${*}" =~ /$ ]]; then
        xargs -rd '\n' -I {} "${@}"{}
    else
        xargs -rd '\n' -I {} "${@}" {}
    fi
    


  • You can only mount into an empty directory. (Edit: Ok that is not really correct. You can mount into directories with content, but then the content will no longer be accessible from that point.) You cannot mix two directories with mount.

    Edit: You could have two points using one Mountpoint at a time maybe. With a script you unmount the fallback, and if you connect the new drive you mount it with the script. And if you are done, use your unmount script to reverse it. Just an idea.

    Some more Edit: In short you create an empty directory that is the Mountpoint, lets say “/home/user/Apple”. Now your real local files are at “/home/user/folderApple”. You mount folderApple to Apple. This is your fallback. Then if you connect the other drive, with your script you unmount that and mount your “/mnt/drive/Banana” to “/home/user/Apple”, which is empty again after the unmount. And reverse it if you want to unplug.



  • This is probably not a huge improvement for Steam gamers with Proton. I would like to see benchmarks on SteamOS using Proton.

    With the provided benchmark results, its notable that they are comparing the new ntsync to the Wine version that has no alternative. Results are impressive. But on SteamOS and Steam in general, we have Proton, not base Wine. And Proton has something else already implemented, that improves performance. Its not as good as ntsync, but my point is, comparing the new implementation in Proton won’t be a huge difference like in the benchmark shown (as the benchmark is comparing Wine, not Proton).