3 ms·
I think you're taking for granted just how performance intensive this is. For example, "Just a blit" is a full screen draw worth of pixel operations on a hardwa
by jayd16 3y ago
I think you're taking for granted just how performance intensive this is. For example, "Just a blit" is a full screen draw worth of pixel operations on a hardware platform that is known to have pixel draw at a premium.
- actionfromafar 3y agoI don't understand this comment. It's a marvel of course how far we have come, but what today is so intensive? The (old!) Apple iPad cable runs BSD Unix and does real time video encoding.
- refulgentis 3y agoCorrect, you're violently agreeing, _they embed a whole *NIX computer in the cable to make it happen_. They were replying to someone saying why does everyone make it so complicated. Refer to my comment for the math on why its intensive
- actionfromafar 3y agoAre you violently agreeing with me now? :-)
- saagarjha 3y agoIt did video encoding because the cable wasn’t capable of streaming full quality video at the required bandwidth. Not because they wanted to make a complicated dongle.
- jampekka 3y agoOf course there are a lot of implementation details that need to be done for the bits to move and the pixels to light up. But the scrcpy code is not about this, it's all hidden behind the libraries and in the hardware. What scrcpy has to do is micromanage and hack the APIs on the both sides for this all to happen in the guts of the systema. I don't see a reason why all this couldn't be done with something like /dev/remote/window < /dev/screen Of course there would be a lot of magic happening at the implementation level, but it's not like you type in all the HTTP protocol and negotiate the compression algorithm manually when you go to a website.