The parent comment is not correct. The Index paired with SteamVR on Linux has a plethora of issues and sometimes doesn’t work at all. It’s usually possible to get it working through some combination of switching SteamVR versions and rebooting, but it’s never a guarantee and usually takes a good chunk of time to get sorted when it’s being temperamental.
It most certainly is not. Besides the missing features mentioned by the other commenter, SteamVR 2.1 literally shipped last week with a bug that caused it to completely stop functioning on Linux. I think the hotfix version still isn’t in the release channel. There’s another bug still present in 2.1.7 that prevents VR games from starting. SteamVR Home doesn’t work at all anymore.
2.0 had an issue where vrdashboard was using the wrong pixel format which caused the red and blue channels to be swapped (pretty sure that made it into the release channel), and there was a regression introduced in the last year (and is still yet to be fixed) that causes vrdashboard to be rendered to the controller instead of the battery indicator. Granted, these are more minor issues, but it shows the level of QA that goes into the Linux version (next to none).
I’m approaching the point where I’m seriously considering buying a spare drive for a Windows install exclusively for VR. I’m currently dealing with 3 separate serious issues with SteamVR on Linux, one of which I sometimes can’t even work around depending on how it’s feeling that day. Not to mention, every new release lately seems to introduce a new problem.
I haven’t had a Windows install on my system since my previous SSD died 2 or 3 years ago, but it’s getting to the point where it’s more trouble than it’s worth.
Just as a note, I believe you still need to tick the “Enable Steam Play for all titles” in Steam settings to allow it to be used with non-verified games.
Public companies are by definition amoral. They’re beholden to their shareholders and virtually every decision they make is informed by this obligation. Morality generally only factors into their decision-making insofar as it affects PR and thus the bottom line.
I don’t mean to say that Google or any other company is immoral. I use amoral to simply mean that they operate independent of morality. No public company, no matter how much you may like them, is your friend at the end of the day.
Chromium is open-source. Chrome is not and also happens to constitute a majority of the browser market, and Google has tried multiple times to cash in on this market share to benefit their primary business of advertising to the detriment of users (FLoC, Manifest v3, Web Environment Integrity).
Likewise, AOSP is open-source, but Google has been progressively dismantling it and making various components closed-source (most recently the dialer app).
All this to say, Google is absolutely not friendly to FOSS. As a corporation, they’re beholden to their shareholders above all else and they should be treated as an amoral entity, the same as every other publicly-traded company.
Nope, different product with almost the exact same name lol.
As another user mentioned, package managers are specific to distributions rather than DEs. The main difference between them is that they’re developed by the respective distribution teams, but there are some practical differences too. For example, apt supports versioned dependencies while pacman doesn’t because of the different distribution models between Debian and Arch (monolithic vs. rolling release). This affects their dependency resolution strategy with each being better suited for it’s respective distribution.
To address your point about package managers being the main difference between distros, this isn’t quite true. As mentioned, different distros have different distribution models, priorities, and overall biases/opinions that affect the user experience in a variety of ways and make them better suited to different use cases. I would never dream of putting Arch on one of my servers in the same way that you’d probably never catch me installing Debian on my gaming machine.
Nah, I did this once and didn’t notice until the call was placed because I was a little tipsy and engaged in conversation. IIRC it didn’t make any noise since my phone is always on vibrate, it just buzzed a bit and by the time I processed what was happening it was too late and I had to explain to the dispatcher that no, I was just fidgeting with my phone.
This article seems to be outdated as both apps are now visible in the Play Store and I had no problems downloading and running them. A comment suggests that it may be due to the previous minimum SDK target for the apps being too low. I’d be willing to chalk this up to being more innocuous than active malice on Google’s part.
Have you used PHP 7+ before? It’s surprisingly ergonomic, much more so than earlier versions.
Why do you count PHP as a point against Kbin?
To Valve’s credit, since that post they did implement base station power management and some DEs now implement Wayland’s DRM leasing protocol, and there’s a somewhat buggy async reproduction implementation in place (although it’s broken in SteamVR 2.0 onwards).