Research into medicine that make the blood/brain barrier function like on healthy people will certainly find applications though, regardless of if it is useful against Alzheimers though.
Essentially, the only games that doesn't work nowadays are the ones that intentionally break it by adding Linux-incompatible anti-cheat. This is common among the big AAA-games that are multiplayer (think Fortnite).
Riot games did this on purpose too. League worked perfectly fine on Linux for years until they decided that kernel level spying on users was absolutely necessary to play a moba. For some reason my one friend thinks I'll run windows just for one game.
I'd sooner get a console, personally. The only legitimate use case I have for a console (nintendo notwithstanding) is to sandbox invasive anticheat in multiplayer games. I don't really have a ton of free time or friend group into multiplayer video games, so it's not happening for me. Smart console makers would lean into this.
Yup, I've also gone with a console for all my gaming needs, and keep my computer as just a productivity machine. As a result I don't need nearly as beefy machine and don't need to grind my teeth in bitterness using Windows.
> ones that intentionally break it by adding Linux-incompatible anti-cheat.
That's an interesting way to phrase it. It's like you're implying the company intentionally did not want to run it on anything but Windows (aka software is incompatible with non-Windows OSes) rather than trying to implement an effective anti-cheat (arguable) that works for their customers.
Pre-Wine, would you have argued that a software vendor is intentionally preventing their software from running on any non-Windows OS?
Or was it just that their audience wasn't on said non-Windows OS?
> That's an interesting way to phrase it. It's like you're implying the company intentionally did not want to run it on anything but Windows (aka software is incompatible with non-Windows OSes) rather than trying to implement an effective anti-cheat (arguable) that works for their customers.
Not OP, but this is true depending on the game. For instance, when Rockstar added BattlEye to GTA V Online, they broke Linux support, and blatantly lied about Linux not supporting BattleEye, when that's just not true - they just needed to enable that option, but they just straight up lied saying BattlEye doesn't support Linux.
> BattlEye on Proton integration has reached a point where all a developer needs to do is reach out BattlEye to enable it for their title. No additional work is required by the developer besides that communication.
So all Rockstar had to do was reach out to BattlEye to enable it, but they couldn't be bothered to do so. Their anti-Linux stance here is pretty obvious.
Rockstar aside, there are other studios/publishers that have been openly hostile against Linux, like Epic for instance - Tim Sweeny has made scathing remarks against Linux, so it's clear where he/Epic stands on that front.
As other comments note there are plenty of problems restricting queues to ordered execution. For most use cases that simply does not matter. What matters are related features like avoidance of starvation or execution bias. And those are perfectly possible to do with multiple consumers/producers.
or C): You cultivate a culture of continuous rewrite to match updated requirements and understandings as you code. So, so many people have never learned that, but once you do reach that state, it is very liberating as there will be no more sacred ducks.
That said, it takes quite a bit of practice to become good enough at refactoring to actually practice that.
Yeah, I think it's actually a great skill to be comfortable with not getting attached to your code, and being open to refactoring/rearchitecting -- in fact, if you have this as a common expectation, you may get really good at writing easily-maintainable code. I have started putting less and less "clever optimizations" into my code, instead opting for ease of maintainability, and onboarding for new team members to join up and start contributing. Depends on the size of project/team (and the priorities therein), but it helps me later too when I have to change functionality in something I wrote anywhere from 6-48 months ago :)
reply