4 ms·
I have three words for you: read the docs. If you're experiencing a bug that pegs you're CPU, fair enough. But RustDesk is video-stream based (in many formats)
by pizza234 2mo ago
I have three words for you: read the docs.
If you're experiencing a bug that pegs you're CPU, fair enough. But RustDesk is video-stream based (in many formats), while TightVNC is image(-region) based. This is actually similar to why you watch movies in, say, H.264 rather than Motion JPEG¹.
¹=similar, not same.
- deleted 2mo ago[deleted]
- diego_moita 2mo ago> I have three words for you: read the docs. No, thanks. As they say: "the proof of the pudding is in the eating". So I used both applications and TightVNC is just a lot better, particularly in constrained remote VMs. Docs are cheap, performance is what matters.
- deleted 2mo ago[deleted]
- embedding-shape 2mo ago> Docs are cheap, performance is what matters. How do you know if the performance you get is the expected, unless you read the docs or at least look at what others get on similar platforms/environments/specs?