ShaunaTheDead

I think upgrading the RAM as you mentioned is going to make a big difference. While the physical RAM might be soldered to the motherboard, you could buy a fairly cheap SD card or USB and set the system up to use that as virtual memory. It won’t be as fast as actual RAM but it might help and large SD cards are honestly really cheap these days.

I just started using Proton, but I don’t think any of their apps are available for Linux natively, which is disappointing. I mostly use Proton apps inside Ferdium which I find useful for combining all of my productivity apps and Ferdium basically just keeps a website loaded, and websites are always cross platform compatible. I would love to know if there’s a timeline for Linux apps in mind.

It’s definitely an edge case by say you’re in ~/ and you run a script like ./code/script.sh then it thinks the current working direct is ~/ rather than what is probably intended which is ~/code/. If your bash script uses full paths like /home/$USER/code/ then it will still run correctly regardless of the current working directory that the scrip was run from.

It really depends whether he got the devs of “Lutris, Heroic, Legendary, Bottles, etc.” to agree to use the unified runtime before starting this project. As long as he gets most of the big players to join then it will actually become the only standard worth using.

I wonder if others have some favourite posters that you they quite often?

For me, it’s @Stamets and ThePicardManuever but I’ve noticed a couple other prominent posters lately although their names haven’t stuck for me just yet.

Gitlab is quite good and used by a lot of open source developers.

You need to learn bash scripting. Also, there are a few default files that the .bashrc uses which can be helpful to compartmentalize the custom things you do to it so that it’s easier to undo if you screw something up. To do that, just add this to the bottom of your .bashrc

if [ -f ~/.bash_custom ]; then
    . ~/.bash_custom
fi

What that will do is check if the .bash_custom file exists and then run the .bash_custom file in your home directory and apply anything in there. Also, you can call the file whatever you like, but bash does have some defaults that it will check for and run them without editing the .bashrc at all. It’s kind of hard to find a list of the the files that it automatically checks for, but I know that .bash_aliases is one of them, and I think it checks .bash_commands as well, but I’m not entirely sure. Either way, you can force it to check your custom one by using the code above.

Then you can create the file and add any custom things in there that you like. For example, I like to frequently update through the terminal but running sudo apt update && sudo apt upgrade && sudo apt autoremove && flatpak upgrade was a bit tedious and I wanted a bit less feedback so I made a custom alias for my personal use.

alias update='echo "Updating packages..."; sudo apt update -y &> /dev/null; echo "Packages updated."; echo "Upgrading packages..."; sudo apt upgrade -y &> /dev/null; echo "Packages upgraded."; echo "Cleaning up packges..."; sudo apt autoremove -y &> /dev/null; echo "Packages cleaned up."; echo "Updating flatpaks..."; flatpak update -y &> /dev/null; echo "Flatpaks updated."'

Which hides most of the text from updating and just gives me feedback on what it’s currently doing if I don’t really care to know all of the details. So now I just run update in the terminal and plug in my password and it updates and upgrades everything in a human readable way.

There’s a lot that can be done with bash scripting, like editing files, iterating over files and directories, setting environment variables. It’s basically a full programming language so the limits are mostly your imagination.

Ezarr is a pretty great little project for getting started. Just clone the repo and follow the README and it should just be plug and play.

Yeah, either put quotes around it ‘/like this/you can incorporate/spaces/into your paths’ or /just\ escape/your\ spaces/like\ this

There is HDMI CEC which allows a single remote control to control all of your devices, so it must be possible for devices connected by HDMI to receive a signal back from the TV.

I’m not sure where you’re getting that idea from. Almost anything designed for Windows works flawlessly through WINE or Proton. If I do run into an issue I usually find that Windows users are also having the same problems so it’s not a Linux compatibility issue. Every once in awhile I’ll have to run winetricks or protontricks to install a dependency. Overall, Linux compatibility is pretty incredible these days, in my opinion.