Sunshine VS ZLUDA

> Would the Swift UI also work on an iPad?

Yes, but probably not for the first version.

> Do you have any comparisons with other tools (eg steam streaming, moonlight)

Steam streaming just doesn't really work on linux. Moonlight is somewhat similar in terms of direction, and has an established client base. I know of at least two projects to build servers for the Moonlight protocol[1][2].

The Moonlight protocol is a bit weird, because it's an open-source reverse engineering of a dead NVIDIA project, GeForce now. There are fundamental limitations to the protocol, for example that the cursor must be rendered in-stream or simulated. Using my tool, the cursor is rendered locally, and custom cursor images can actually be pushed to the client, for a seamless experience. This sounds like a minor detail but it matters a lot for subjective latency. I'm also working on employing tricks like hierarchical coding using FEC in the protocol, because I hate VBR encoding for games (it makes text blurry and breaks immersion). Those tricks aren't really possible in Moonlight.

All of the Linux solutions I know about have significantly higher latency compared to Magic Mirror, although I don't have numbers for exactly how much higher. (I have a benchmark to test the latency of my tool, but the others don't.) I'd encourage you to try them out and get a feel for the difference.

Finally, I think Magic Mirror is the easiest to install and get going on the server. It has almost zero runtime library or service dependencies (there's a pesky dynamic link against libxkbcommon which I haven't managed to remove), so you don't need to mess with pipewire or docker or anything - it's completely self-contained.

All that said, the existing tools have the advantage of a larger user and contributor base, whereas Magic Mirror is just me on a mission so far :) So they're likely to be much more stable and usable.

[1]: https://github.com/LizardByte/Sunshine

RDP as a regular or quick solution is actually really decent in this respect.

(1) https://app.lizardbyte.dev/Sunshine

Moonlight + Sunshine for a self hosted solution, works with every OS

server: https://github.com/LizardByte/Sunshine/

client: https://github.com/moonlight-stream

You could use sunshine (https://github.com/LizardByte/Sunshine) + moonlight (https://github.com/moonlight-stream/moonlight-qt). To be honest, at least for me, it works better than most of the RDP/VNC stuff.

EDIT: Just checked again, original was released early 2020, current maintained project started 2022.

On your pc, install Sunshine. It's an open source moonlight server. There's a good walk through on the sunshine github page. Connect your handheld to the wifi running the server & open moonlight. Should work.

I discovered the moonlight client and sunshine server a few months ago. These are open source solutions to provide remote gaming/desktop capabilities with built in input and audio passthrough. I tried NoMachine, but I wasn't able to get audio to work. This looks like a known issue on arch. On sunshine, I didn't have to do any extra tweaking! This allowed me to game on my desktop pc without having to sit at my desk. This was especially helpful while watching my 2nd son. I was really impressed by the performance, I could stream my host's display at high resolutions and frame rates with low latency despite my desktop being in the basement using WiFi. I was getting some instability with WiFi, so I wanted to try connecting my desktop to the router via Ethernet. I decided to go with a headless solution because that gives me more flexibility on the placement of the desktop; I ended up moving my desktop upstairs closer to my router. I figured out a way to stream my hosts display headless by using Nvidia TwinView to create the virtual display. This means I don't need to buy any HDMI/DP dummy plugs. I wrote a Linux Guide for sunshine on how to set this up. If you have any feedback on this guide, let me know! I haven't tried this, but wolf is an interesting docker alternative to sunshine.

It now supports AMD GPUs since 3 weeks ago, check the latest commit at the repo:

https://github.com/vosen/ZLUDA

The article also mentions exactly this fact.

Looks like nvidia is trying to keep the lynchpin of their entire business model from crumbling underneath them. ZLUDA lets you run unmodified CUDA applications with near-native performance on AMD GPUs.

https://github.com/vosen/ZLUDA

With Triton looking to eclipse CUDA entirely, im not sure this prohibition does anything more than placate casual shareholders.

>Dark API functions are reverse-engineered and implemented by ZLUDA on a case-by-case basis once we observe an application making use of it.

https://github.com/vosen/ZLUDA/blob/master/ARCHITECTURE.md

> I know AMD have their competition, but their GPU software division keeps tripping over itself.

They are actively stepping on every rake there is. Eg they just stopped supporting the drop-in-cuda project everyone is waiting for, due to there being "no business-case for CUDA on AMD GPUs" [0].

[0] https://github.com/vosen/ZLUDA?tab=readme-ov-file#faq

https://github.com/vosen/ZLUDA

They still funded it and it was created.

From the same repo, I found this excellent, well-written architecture document: https://github.com/vosen/ZLUDA/blob/master/ARCHITECTURE.md

I love the direct, "no bullshit" style of writing.

Some gems:

> Anyone familiar with C++ will instantly understand that compiling it is a complicated affair.

> Additionally CUDA allows, to a large degree, mixing CPU code and GPU code. What does all this complexity mean for ZLUDA? Absolutely nothing

> Since an application can dynamically link to either Driver API or Runtime API, it would seem that ZLUDA needs to provide both. In reality very few applications dynamically link to Runtime API. For the vast majority of applications it's sufficient to provide Driver API for dynamic (runtime) linking.

CUDA is huge and nvidia spent a ton in a lot of "dead end" use cases optimizing it. There have been experiments with CUDA translation layers with decent performance[1]. There are two things that most projects hit:

1. The CUDA API is huge; I'm sure Intel/AMD will focus on what they need to implement pytorch and ignore every other use case ensuring that CUDA always has the leg up in any new frontier

2. Nvidia actually cares about developer experience. The most prominent example is Geohotz with tinygrad - where AMD examples didn't even work or had glaring compiler bugs. You will find nvidia engineer in github issues for CUDA projects. Intel/AMD hasn't made that level of investment and thats important because GPUs tend to be more fickle than CPUs.

[1] https://github.com/vosen/ZLUDA

> I don't think you understand just how insanely difficult it is to break into that market.

You're right, I have no clue nor have I ever tried myself.

> Even with apple money or something like that, it's a losing prospect because in the time it'll take you to get up and off the ground (which is FOREVER) your competition will crush you.

This I find hard to believe, do you have a source or reference for that claim? Companies with that amount of cash are hardly going to be crushed by competition be it direct or indirect. Anyway, I'm talking more about the Intels and AMDs of this world.

We have very lacklustre efforts from players I won't name with their Zluda library (https://github.com/vosen/ZLUDA) which I got REALLY excited about, until I read the README.txt. Four contributors, last commit early 2021.

Why, oh why, is it this bad?