

Ahh, you have the new install. Yes that is a known issue. I was installing it before they did the switcheroo with their custom distribution QT6 webview (the root cause of the issue). If you have the old install it still works just fine


I imagine if you play MSFS you have a beefy PC to handle Affinity through WINE


Check out the proton rating site for space engineers. I forgot the specific but there’s a command line and proton version that works best for it. Another valid option is to have dual compositor (I use plasma and gamescope) since you can easily choose that on the login screen.


Affinity works using WINE. I think there also exists a repo where they packaged it into .appimage


Affinity can be installed on Linux via WINE just fine. There’s even a repo for it. Fusion360, of all things, also works the same way. WINE is not just for gaming


Also I don’t understand why we need to have a .env file in the first place when config file exists and best practice to pass on secret is not with .env file anyway.


I can already feel that my Cooler Master mouse 2.4GHz dongle doesn’t need to get restarted / replugged every so often


It MUST spread. Like the article said, we should speak up and spread it anywhere we can. This is a good way to fight the legislation by playing by the rules


I’m being pedantic here but RISC-V is not a hardware architecture as in something that you can send to a manufacturer and get it made. It is an ISA. How you implement those ISA is up to you. Yes there are open implementations but I think it is important to distinguish it.
You store git repo in your documents?!