Linux is all good if you only play singleplayer games. My friends started playing the finals yesterday and it doesn’t run on linux because of EAC. Windows can run all my games without any proton switching and all the nvidia features like ray reconstruction and pathtracing with frame generation just works (alan wake 2 looks so good).
Just FYI, the expression makes more sense the other way around:
And yeah, dual booting is absolutely a thing. That said, I find rebooting to play a game silly, so I just avoid stuff that doesn’t work on Linux. I can totally see the opposite perspective as well.
…how else would you go about eating it? Smashing your face into the whole cake?
The point is you can’t eat your cake and still have it afterward, because it has been eaten. So the more common version OP referenced makes no sense because you obviously need to have your cake before you’re able to eat it, so it’s unclear what you’re trying to say.
Can I have some cake?
Sure, here you go. You can go ahead and eat it, too. Go on. It’s chocolate.
*having cake and eating it, too.
Right, but then the cake is gone and you don’t have it anymore, you just have a plate with crumbs. That’s what the adage is trying to convey (you can’t have it both ways). Either you save your cake for later, or you eat it not, you can’t do both.
My linux usually boots very fast while Windows takes its sweet time, but still within 5m from power on to everything is up and warmed up.
So not something that stops me from rebooting to play a particular game
It’s not boot time, but context switching (close apps and whatnot). I suppose I could hibernate, but I still lose access to my network services, like my kids’ Minecraft server and network shares. And then Windows usually has massive updates because I launch it so rarely.
If I play on Linux, I just launch the game, and that’s it.
Before Steam came to Linux, I just didn’t play games very often. Now that most games work, I can just push play and I’m in a game, so I play a lot more games.