Live data from Hacker News

Valve is paying open-source developers to work on Proton, Mesa, and more

old.reddit.com

131–140 of 288 posts

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#131
post #4

I bought Steam games and a Steam Deck just to support Valve... and I'm not really a gamer. However, the Deck has turned out to be a pretty good computing device.

I was thinking of doing this - how do you like it? How's coding on it?

It's definitely great to support Valve in their efforts, but you all might be interested in GPD's lineup of small computers, because many of them have built-in keyboards:

https://gpd.hk/product

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#132
post #10

Linus at DebConf 2014 https://www.youtube.com/watch?t=310&v=Pzl1B7nB9Kc&feature=yo... >I’m on a record saying, that maybe Valve will actually save the Linux desktop. And it’s actually not because I think games are important! I don't care, I don't play games. I think some people do, so games maybe important. But the really important issue is I guarantee you Valve will not make 15 different binaries. And I also guarant…

didn't valve mostly mitigate the fat binary problem with their soldier runtime set of shared libs?

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#133

Earlier quoted context omitted.

Nix is effectively transforming dynamic binaries to static ones. Might as well skip the step, stop pretending that drive space is expensive, and link everything statically.

Huh, never heard it put this way. I guess it's true though. Anyone disagree?

Conceptually that's kind of true, if you only consider the end result for a given binary, (since it would load only shared libs as if they were statically linked).

But multiple derivations can share dependencies, which does save space and also makes it easy to identify dependencies of a given derivation, where statically linking would make that opaque.

Also, the story goes way beyond binaries, as dependencies often carry additional resources not bundled into the binary.

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#134
post #60

Earlier quoted context omitted.

They actually did in the past, but they've realised that many game devs can't be trusted to maintain Linux builds as a second platform. They're often left outdated, require dependencies they didn't ship with or simply have worse performance than the Windows builds running on Proton. These days they check both builds if available and suggest the devs which one to use by default; often the Windows builds over Proton ar…

The same devs that most likely are also shipping Playstation or Android versions of their game....

Orders of magnitude bigger markets.

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#135

Earlier quoted context omitted.

Id rather have static binaries than a flatpak/snap for "universal distribution", personally.

Given the choice I prefer native package -> AUR package -> AppImage -> Flatpack, in that order. (snap, you'll notice, is absent) Arch is pretty good at making the native packages work, so that's always ideal. The community is generally pretty good at competently packaging AURs, and they'll do it for slightly less free things, so that fills a lot of gaps. AppImages and Flatpaks are great when they work, but opaque and…

Why AppImage over Flatpack? I like the Flatpack ability to easily restrict network access to binaries. Probably possibly in all of the packaging formats, but limiting permissions feels like a functional piece of Flatpack.

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#136
post #16

Is Valve the only company in the world that is not universally hated by the HN and reddit crowd?

There are many. Mozilla isn’t universally hated. Apple is another. I’d say Valve comes close to being universally loved here, though, and that is pretty unique.

Apple is a weird one from my perspective. I dislike Safari, but overall I'm pretty ambivalent about Apple in general. But most devs I've met IRL seem to despise them, while HN seems to mostly have a positive view.

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#137
I'm one of the developers contracted by Valve to work on gamescope, wlroots, Mesa, the kernel, Wayland, etc. Really happy that my contracted work helps not only SteamOS, but very often the whole ecosystem. Examples include radv/amdgpu fixes, tearing page-flips, a re-usable library to make use of KMS planes, and the list goes on.

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#139

Earlier quoted context omitted.

Many games rarely update, though. They put out the original version, and then maybe a few patches to fix game-breaking bugs, and then that's how they exist from then on. If you're expecting them to update to address vulnerabilities, you're going to be very disappointed. That said, if the library changes the API or functionality at all, dynamic linking is going to break the game, and that's not good either. So gamedev…

For single-player games, I doubt it matters if there are unpatched vulnerabilities.

Many single player games do still phone home or otherwise cause network activity, so it’s not like they are guaranteed a safe bubble in which to run.

Re: Valve is paying open-source developers to work on Proton, Mesa, and more

#140
post #128
post #51

Earlier quoted context omitted.

Right now I'm stuck with nVidia's Jetson line of products which is vendor-locked to Ubuntu. The problem is that while you can extend them with a large SSD drive, these products have a really small disk used for /. I could run another OS inside a Docker container, all to avoid this limitation in snap, but of course things will not become prettier.

You can change the root parameter in extlinux.conf to point to whatever block storage you want it to Or reconfigure U-Boot to load extlinux.conf (and the kernel image, initrd, etc) entirely from other type of media. IIRC NVMe, USB and external SDs are all supported

Thanks, I'll have to look into it.
Post reply on HN