The Newscast is not the images. It’s an annoying video they embed in all articles and then floats when you scroll. I actually have set an adblock rule to block that shit.
As for the images, for now hotlinking to Twitter images is possible, so:
In some far future, sure. But at the moment Linux barely makes up 2% of the users
Fun fact: Whenever a console maker launches a new console, ahead of launch the user base is 0.000000000000000000000000000000000000000000000000000000000000000000000000000000000%. And yet no one of them would even think about not incentivizing game development for the upcoming platform.
and that number is not going to rise if developers started developing natively for Linux.
Based on which argument? Games on occasion break on updates. Players get banned for using Proton. That’s negative publicity.
There is currenttly negative incentive for developers to develop natively for Linux, I can’t find the article but there was a developer who ported their game to Linux and while Linux was barely a speck of their playerbase the Linux users made up the majority of support tickets.
Doesn’t change the fact that native games lead to a better experience for consumers (which I already outlined).
Valve would need insane incentives to get developers to develop for Linux. Or they could take fraction of that effort and make Proton better.
Start by offering a proper SDK that plugs into Visual Studio. You’re acting as if incentivizing would cost insane amounts of money, based on no fact at all.
Quite frankly I’m not sure why I even need to explain this
You barely explained anything. I explained why emulated Windows games lead to worse user experience. You refuted nothing of that.
So you understand that it is way more beneficial for Valve to support proton than native Linux, and then say that Valve should incentivize native builds?
Proton should be the focus for older, existing games and native games should be the focus for new games. Not really that hard to understand.
I think you’re missing the point. It’s not about OS backwards compatibility, it’s user library backwards compatibility.
I never proposed to ax Proton, so I’m not the one here missing any points.
It’s also why they don’t need to incentivize native builds, because they already solved that problem on their own with Proton. Why put effort into having developers develop native builds when you could just put that effort into Proton and essentially get the same result (and extra benefits) without hoping the developers do something they didn’t want to do in the first place?
I explained several times already that game updates breaking Proton compatibility is a real thing that would not have happened with native games.
Game developers develop for dedicated platforms other than Windows all the time. They’re called game consoles. Native games don’t just mysteriously break on updates or suddenly ban players because the game developer out of the blue decided that Proton is cheating. First launch of games doesn’t annoy with those stupid Microsoft runtime installer scripts, etc. Proper native games could be optimized the way console games are instead of relying on multiple levels of Windows compatibility layers (the newest BS Proton has to deal with is gamepad compatibility for launchers via a special input wrapper) – they are just a smoother experience all around.
I see you don’t know about Steam Linux Runtimes which are backwards and forwards compatible. 1.0 (“scout”) is based on Ubuntu 12.04, so already 12 years of binary compatibility.
Valve could start by releasing a Steam Deck SDK for Visual Studio that exposes an “Export to Steam Deck” option when targets the latest release of Steam Linux Runtime.
Currently they offer Docker containers which is good but could be improved.
Back when Steam Machines were a thing and Valve tried to only push Linux native games, game developers got placements on Steam Store’s landing page banner in return.
Valve leaving the Mac Steam client a slow and laggy mess on newer Macs.
What happened to the Apple fanboys who claimed that the Apple M processors were so fast, x86 applications emulated on Apple M would run much faster than natively on x86 because x86 is supposedly so bad and slow…?