Yah. Makes more sense for Valve to spend their time improving Proton or working on their reference handheld device. A reference desktop device is a solution looking for a problem.

They’re completely different implementations of systems that steam video/audio/inputs.

Valve’s is pretty buggy but has deep integration with Steam and allow NAT traversal, while Sunshine/Moonlight are way more reliable, have features that reduce latency but are pretty barebones as far as features: they just do streaming with no tight integration with what’s being streamed.

And Sunshine is a reverse engineered version of Nvidia’s game stream server, since Nvidia sunset Gamestream a few months ago.

tl;dr - Second option usually.

I think a huge part of shell programming (besides recognizing when anything more maintainable will do 😂😂😂) is trying to allow others who aren’t as familiar to maintain what you’ve written. Shell is full of pitfalls, not the least of which is quoting and guaranteeing how many arguments you pass to commands and functions.

To me, the whole point of quoting here is to be crystal clear about where command arguments begin and end in spite of variable substitution. For this reason I usually go for the second option. It very clearly describes how I’m trying to avoid a pitfall by wrapping each argument to find in a pair of quotes: in this case, double quotes to allow variable substitution.

Sometimes it’s clearer to use the first approach. For example, if the constant parts of one of those arguments contains a lot of special characters, it may make it clearer to use the first approach with the constant parts wrapped in single quotes.

But even then there are more clear ways to create a string out of other strings. For example, the slightly slower, and more verbose use of printf and a variable, and then using that variable as an argument…wrapped in double quotes since it could contain special characters.