cm0002@mander.xyz to Programming@programming.dev · 2 days agoWe Mass-Deployed 15-Year-Old Screen Sharing Technology and It's Actually Betterblog.helix.mlexternal-linkmessage-square51fedilinkarrow-up1181arrow-down127cross-posted to: programming@lemmy.ml
arrow-up1154arrow-down1external-linkWe Mass-Deployed 15-Year-Old Screen Sharing Technology and It's Actually Betterblog.helix.mlcm0002@mander.xyz to Programming@programming.dev · 2 days agomessage-square51fedilinkcross-posted to: programming@lemmy.ml
minus-squareeco_game@discuss.tchncs.delinkfedilinkarrow-up10arrow-down1·2 days agoFrom what I read, the modern solution has smooth 60 fps, compared to 2-10 FPS with the JPEG method. Granted, that probably also factors in low network speeds, but I’d imagine you may hit a framerate cap lower than 60 when just spamming JPEGs.
minus-squareMadhuGururajan@programming.devlinkfedilinkEnglisharrow-up5·2 days agoyou don’t need 60 fps to read text? All you need is to stream the text directly?
minus-squareAatube@thriv.sociallinkfedilinkEnglisharrow-up2·1 day agoit seems like they sometimes need to stream the finished app coded, too (still no need for 60 fps…)
From what I read, the modern solution has smooth 60 fps, compared to 2-10 FPS with the JPEG method. Granted, that probably also factors in low network speeds, but I’d imagine you may hit a framerate cap lower than 60 when just spamming JPEGs.
you don’t need 60 fps to read text? All you need is to stream the text directly?
it seems like they sometimes need to stream the finished app coded, too
(still no need for 60 fps…)