Handheld PC makers are slowly losing touch with Valve's successful Steam Deck template of affordability, and that's very concerning
-
This post did not contain any content.
they’re also forgetting the touchpads. the touchpads are so fucking good, and they add so much usability and flexibility. so much, I think, that no amount of superior performance, resoution, or battery life can make up for the lack of them.
-
No, Wine (and Proton) is a compatibility layer (API translation, etc). Containers is an isolation method which hides the details of the OS from the software and gives it a standardized environment.
GitHub - ValveSoftware/steam-runtime: A runtime environment for Steam applications
A runtime environment for Steam applications. Contribute to ValveSoftware/steam-runtime development by creating an account on GitHub.
GitHub (github.com)
No matter what Linux distribution you run Steam on, the only thing you need to do is to get the container system up and running. Once that runs, all software that runs in these containers will run on that device.
So something akin to flatpak/snap?
Isnt that the purpose and source of controversy vs distributing them the usual way of repositories?Edit: Had some time to read the README.
Very interesting. But that sounds, like a vendor lock-in. Essentially devs are forced to use the Steam SDK to make it executable on Linux or face the issue of checking the compatibility of every distro, no? -
This post did not contain any content.
That title is cringe as fuck. There’s nothing concerning about it at all. Market saw Steam Deck’s success so they dove in. Whether they survive is dependent on if they provide good price points or justification for a higher price. Super simple.
-
they’re also forgetting the touchpads. the touchpads are so fucking good, and they add so much usability and flexibility. so much, I think, that no amount of superior performance, resoution, or battery life can make up for the lack of them.
Absolutely. They make mouse-based games playable with a controller. Gyro is nice too.
-
When talking about a container environment you are talking about WINE, arent you?
But if we are talking about native developed games, how would that look?
That sounds to me like 1st priority-development will be continued using Windows as a base + DirectX and reliance that WINE will somewhat manage that.
How would native Linux look for game devs in terms of platform targeting?You might want to catch up on a decade or so of Linux gaming progress before wading into a conversation about it with controversial takes…
-
So something akin to flatpak/snap?
Isnt that the purpose and source of controversy vs distributing them the usual way of repositories?Edit: Had some time to read the README.
Very interesting. But that sounds, like a vendor lock-in. Essentially devs are forced to use the Steam SDK to make it executable on Linux or face the issue of checking the compatibility of every distro, no?You don’t need to use Steam to run games though…?
-
they’re also forgetting the touchpads. the touchpads are so fucking good, and they add so much usability and flexibility. so much, I think, that no amount of superior performance, resoution, or battery life can make up for the lack of them.
This is why I bought a deck oled even with the other more powerful handhelds already out.
-
You might want to catch up on a decade or so of Linux gaming progress before wading into a conversation about it with controversial takes…
Why?
A discussion can’t happen.
And you don’t really expect everyone to be knowledgeable about every 500 aspects of every OS that can execute a program, do you?If I was invited to a discussion round, I will obviously get myself up to date on the essentials.
But I already do sysadmin stuff at work, configuring multiple systems, administrating my home stuff the best I can.
I really don’t have the mental energy to keep up with an OS I currently only use as a server OS and as a (basically) gaming appliance. -
You don’t need to use Steam to run games though…?
So what if Steam stops development of the SDK or turns evil?
What other choices do devs have if they want to keep their systems compatible with all distros?
It looks to me as if you can either rely on proton/WINE or be stuck with the SDK if you run native. -
Other manufacturers do not have that luxury.
They can find some margin in using a rolling Arch distro instead of paying for Windows, Gabe helpfully provided the template that you can reuse.
That still does not magically give them a digital storefront that the consumer will use to purchase a ton of software that gives then a 30% cut.
Yes, technically you can purchase and use a Deck without purchasing a single game on Steam. But how likely is that? Valve has done the math and made their projections and concluded that selling the Deck roughly at cost (my assumption based on their vague statements and industry comparisons) will increase software sales in Steam. And increase profits more than if they had priced the Deck at a highrt margin selling g desert units and driving less software sales.
Lenovo and ASUS and these other manufacturers don’t have that. An operating system change will not fix issues with the business model and ecosystem.
-
Sell 15K units at 900 a pop, or sell 150K units at 500 a pop…
We don’t know the margins on these things but I’d think that higher volume sales would be better. But what do I know.
Margins could be 0 or even negative.
Sony for example: every single PlayStation has always been released at a price below cost. This allows them to create an ecosystem with a very large user base buying software, where even in 3rd party titles they at least bring in license fees.
Sony then invests those profits into scaling, improving, and redesigning the PlayStation to reduce costs, which is why the do slim models.
-
This post did not contain any content.
It’s called enshitification, we knew it was coming.
-
So something akin to flatpak/snap?
Isnt that the purpose and source of controversy vs distributing them the usual way of repositories?Edit: Had some time to read the README.
Very interesting. But that sounds, like a vendor lock-in. Essentially devs are forced to use the Steam SDK to make it executable on Linux or face the issue of checking the compatibility of every distro, no?No, the container environment uses default open source libraries. You don’t add any Steam dependencies to make software run in that environment. You can run it without Steam too. It’s just that Valve are the ones maintaining and updating this particular packaging of containers. When Valve releases new versions of their container (including updated default system libraries), you have to test compatibility with it or stick to using an older one. Similar to how Windows software versions would work best with different Proton versions.
You can use the Steam SDK when using it, and you can also choose not to.
Flatpack is a separate thing, which only handles Linux software within the regular desktop environment (a different method for packing software dependencies, managing system permissions, etc). The main difference is that Flatpack software can integrate with the regular Linux desktop environment, but the container based solution is fully separate from it (runs in gaming mode).
-
So what if Steam stops development of the SDK or turns evil?
What other choices do devs have if they want to keep their systems compatible with all distros?
It looks to me as if you can either rely on proton/WINE or be stuck with the SDK if you run native.Proton often works better than native Linux versions of the same game.
Just use Proton. Seriously, if you haven’t gamed on Linux in a long time, it’s mind blowing how well it works.
-
This is why I bought a deck oled even with the other more powerful handhelds already out.
I have the OLED too and it’s such an exceptional device. Works very well as a media PC too, especially with KDE Connect for controlling remotely from a smartphone
-
Absolutely. They make mouse-based games playable with a controller. Gyro is nice too.
Not just playable but pleasant! Thing is perfect for Rimworld especially
-
I haven’t played RimWorld on Deck yet… Sounds like a good way to lose entire days.
-
I have the OLED too and it’s such an exceptional device. Works very well as a media PC too, especially with KDE Connect for controlling remotely from a smartphone
It’s so nice fr, it helps I had sorta “prepared” by learning Bazzite on my spare laptop prior, so got very familiar with the immutable aspects and flatpaks/appimages
-
Proton often works better than native Linux versions of the same game.
Just use Proton. Seriously, if you haven’t gamed on Linux in a long time, it’s mind blowing how well it works.
Like I mentioned: I am gaming quite a bit (lately more on it than on my regular PC) on my SteamDeck.
-
No, the container environment uses default open source libraries. You don’t add any Steam dependencies to make software run in that environment. You can run it without Steam too. It’s just that Valve are the ones maintaining and updating this particular packaging of containers. When Valve releases new versions of their container (including updated default system libraries), you have to test compatibility with it or stick to using an older one. Similar to how Windows software versions would work best with different Proton versions.
You can use the Steam SDK when using it, and you can also choose not to.
Flatpack is a separate thing, which only handles Linux software within the regular desktop environment (a different method for packing software dependencies, managing system permissions, etc). The main difference is that Flatpack software can integrate with the regular Linux desktop environment, but the container based solution is fully separate from it (runs in gaming mode).
Sounds interesting and eases my concern about the dependency on large corporations.
PS: What I meant by comparing Flatpack with the packaging from the SteamSDK is the general idea behind it (e.g. containerizing and isolating from the OS).