I shutdown my Desktop daily, sometimes more if for example I’m playing in the morning and going out for lunch and coming back in the evening and playing again. In short if I’m going to spend over an hour not using it I’ll power it off, no reason to keep it on and honestly it powers on almost as fast as coming back from hibernation so why bother? That made sense before SSDs, but nowadays I don’t see much reason.

There’s one big exception, and that is sleeping in the middle of a game, to be able to be back in the game in seconds. It’s one of my favorite features of the Steam Deck, but I haven’t tried it on my desktop because I usually use it for other stuff too so it’s not as useful there.

But what is a trusted provider? How can you trust it? How sure are you that you’re not being MitM? Have you fully manually verified that there’s no funky flags in curl like -k, that the url is using SSL, that it’s a correct url and not pointing at something malicious, etc, etc, etc. There are a lot of manual steps you must verify using this approach, whereas using a package manager all of them get checked automatically, plus some extra checks like hundreds of people validating the content is secure.

To do apt get from an unknown repo, you first need to convince the person to execute root commands they don’t understand on their machine to add that unknown repo, if you can convice someone to run an unsafe command with root credentials then the machine is already compromised.

I get your point, random internet scripts are dangerous but random internet packages can also dangerous. But that’s a false equivalence because there are lots of safeguards to the packages in the usual way people install them, but less than 0 safeguards to the curl|bash. In a similar manner, if this was a post talking about the dangers of fireworks and how you can blow yourself up using them your answer is “but someone can plant a bomb in the mall I go to, or steal the codes for a nuclear missile and blow me up anyways”.

But those are two very different things, I can very easily give you a one liner using curl|bash that will compromise your system, to get the same level of compromise through a proper authenticated channel such as apt/pacman/etc you would need to compromise either their private keys and attack before they notice and change them or stick malicious code in an official package, either of those is orders of magnitude more difficult than writing a simple bash script.

You didn’t knew that the tool to handle URLs written in C (very creatively named C-Url) was handling URLs? It’s also written in C if you didn’t knew.

Sure, but which OSD criteria is being broken here?

Open source and FOSS are two different things though. I think Mattermost is open source, just not FOSS and the licencing they mentioned might be wrong (GPL is invasive so they couldn’t have a closed source part IIRC), but it’s still open source as the code is freely available.

That’s a very cool idea, seems great for receipts and quick stuff.

While this might be true, there’s a big difference in using LLMs for auto-completions, second opinion PR reviews, and maybe mocking up some tests than using it to write actual production code. I don’t see LLMs going away as a completion engine because they’re really good at that, but I suspect companies that are using it to write production code are realizing/will soon realize that they might have security issues and that for a human to work on that codebase it would likely have to be thrown away entirely and redone, so using slop it only costed them time and money without any benefits. But we’ll see how that goes, luckily I work at a company where managers used to be programmers so there’s not much push for us to use it to generate code.

How does it work on Android? One of my main use cases for Nextcloud is to be able to access some of my pdfs on my phone, the app seems to be focused on uploading which is something that while I do sometimes from my phone is much less often.

Warning, I’ve had an issue in the past where I couldn’t play a game (Deus Ex Mankind divided) because it needed a specific instruction set on the CPU (SSSE3). While not your specific case since the FX-8350 supports SSSE3 (I should know, that was the exact CPU I switched to to be able to play the game) there might be newer instructions sets that this old CPU does not support.

Also that GPU is older than what people like to remember, from a time where AMD was the worst GPU option on Linux. It’s very likely that the open source driver is good enough for that card by now, but there’s a good chance you might need to wrestle with the AMD proprietary GPU driver (fglrx) which is worse than the Nvidia one in some aspects and some distros don’t even package it anymore.

If you plug your Nvidia GPU that rig would be usable for gaming, I’m not sure what fps you would get as games keep getting updates and old hardware remains the same so old benchmarks might not be reliable, but I suppose it should run plenty of stuff.

You used Linux like Windows and got bad results, OP treated Windows like Linux and got bad results. The problem is neither OS but how familiar you are with it and their peculiarities.

That being said, GPU drivers are not a rough edge on Linux, only Nvidia drivers are. And even then it’s usually a single click/command to install the proprietary drivers if you need them, otherwise the open source ones work like a charm. This used to be more of a problem a few years back, when both manufacturers used proprietary drivers, but AMD ones are open now and therefore integrated into the mainstream kernel, so they just work.

Yes, but you would need to know to run that command, so it’s the same situation as the windows case where he didn’t know which drivers to get. So the argument is disingenuous in that it either ignores the case or he has knowledge on one OS that he doesn’t on the other. On the other side of the coin someone could be making a similar post saying in windows they just switched hardware, installed drivers and done, in Linux they spent hours trying to figure out how to install the drivers.

I’m not saying it’s hard (on any OS) but it requires previous knowledge on both (although to a much lesser extent on Linux since this only happens when switching GPUs and only under specific conditions).

Can you give me an example of which distro/hardware change gave you a black screen? Because unless it was Gentoo or something you built the kernel yourself a black screen is extremely unlikely. Unlike Windows which requires drivers for everything, in Linux the drivers are baked into the kernel, so any hardware change should just work out of the box (there are some caveats to get the best possible driver, but even the included driver should be more than enough for almost anything except heavy use on Nvidia GPUs).

I agree that on average the Linux user has more technical expertise than the average windows user, but that’s mainly because the average user doesn’t choose their OS. If you take into consideration only people who actually chose their OS, I think it’s very similar.

And OP talked about his experience doing that, the default windows driver gave him a crappy resolution, and he had lots of issues getting the right driver and making it work. You skipped all of those issues because you knew beforehand which was the correct driver, and pre-downloaded it.

This is disingenuous, if you had an AMD GPU on Linux and switched to an Nvidia card you would be using the nouveau drivers so you would need to install the proprietary drivers to get the best performance.

And lots of the same issues that are listed on the windows side could happen on Linux as well since they relate to connectivity.

I agree that the original post is dishonest, but your solution is exactly the same as what they said with the exception that you knew it would be a problem so you downloaded the driver beforehand. Had you not known that would happen the series of misfortunes could have happened to you too.

Because you brought up a non-proton related issue. It’s highly unlikely this is proton related, this is an issue on how the steam virtual keyboard and Skyrim interact, and since the keyboard doesn’t cause issues on any other game I think it’s very likely the culprit is Skyrim, and if that’s the case I want to know if the issue also happens on Windows.

Is it possible that the issue is within proton? Yes, but the problem you presented can be in multiple other places that proton can’t touch. For example if the game crashes on windows too then proton is working correctly, and even if it doesn’t it can still be something else besides proton, e.g. steam closing the keyboard in a different manner, Skyrim has had a famous bug where it crashes when you alt+tab away from it and come back on Windows for a long time, and opening a virtual keyboard on top of the game and going back is essentially alt+tabing, so I wouldn’t be surprised to find out that this is the same bug in Skyrim showing up with a different face.

PS: out of curiosity I went and loaded my old prisoner save, and named the character which is how many people reported the bug and it just worked, so even if this used to be an issue, doesn’t seem like it is anymore.

What happens when you do that? And does doing that on windows work? Because it sounds like an incompatibility between the steam virtual keyboard and Skyrim.

Ansible.

I use docker for most of the services and Ansible to configure them. In the future I’ll migrate the server system to NixOS and might slowly migrate my Ansible to NixOS, but for the time being Ansible is working with relative ease.

Yeah, I was talking about the community in the last paragraph. The tool makes easier official ports and also allows unofficial ones (which works as an encouragement to studios to make the port official).

You’re completely missing the point of this. Oculus Quest uses an Android OS, which means every VR game released for Oculus Quest is an APK, which means there’s a version of the game already optimized for a portable VR headset that can be run with Waydroid/Lepton. Valve is making the same move they did with the Deck, we can’t convince studios to build native? Okay, we’ll run whatever version it is they have already published.

This in conjunction with Fex makes it so that they should be able to run any VR game that could possibly be run in the limited hardware, and they’re giving studios a way to release a “native” version that they already have laying around for better performance (or even to make their first release on Steam).

And let’s not forget side-loading, most games on the Quest have already leaked their APK, they don’t care too much because they’re the only Android portable VR, but because the frame is an open platform people would be able to just install those files manually very easily. So if the studios won’t do the minimal effort to bring their games to the frame the community will. I was momentarily sad when I realized that robo recall (which I own for the Oculus Quest) is not available on Steam, less sad now.