4 ms·

What tech is the remote desktop based on? VNC? Quite curious about how you keep the latency low enough that it to type in an editor.

by devxpy 7y ago

greggman2 7y ago
Windows Remote Desktop has been usable or at least not completely unacceptable in the past. VNC though I've never seen it be acceptable for CAD so I'm curious too.
- edunteman 7y ago
  Windows Remote Desktop is the current tech in Booste, and is useable but not necessarily pleasant, I admit. Engineering priority #2, following multi-device-support, is to tackle the streaming challenge. I'm trying my best, as a solo founder, to not build out features until they're requested, so consider "Faster Streaming" to be requested!
emmelaich 7y ago
Apparently Citrix according to another comment. I thought it might have been https://www.spice-space.org/ https://www.spice-space.org/ which is GPL2. Amazon workspaces seems to use RDP
- edunteman 7y ago
  I encourage users to use their Windows RDP client for this version.
- balakk 7y ago
  Workspaces uses PCoIP AFAIK
  - dillonmckay 7y ago
    I wish mobile OSs had an implementation of this or similar.
edunteman 7y ago
I actually have not engineered the streaming portion, so latency is the same as current VNC and RDP protocols. To get the product together as fast as possible (first line of code written three months ago), I actually did not reengineer the remote desktop protocol. In fact, the current product simply gives you the IP and password info to plug into your Windows Remote Desktop client app. Future plans are to integrate RDP into the Booste app, to make the experience seem more native. After that, I'll be implementing the modern H.265 protocol used by videogame streaming companies such as Vectordash and Nvidia GeForce Now.
- mgamache 7y ago
  h.265 will require hardware compression on the encode side (GPU) so you'll have to factor that into the cost.
  - edunteman 7y ago
    For sure! Glad to have the tech insight. I already tether a GPU to the encode side for the 3D design apps, but I'll certainly need to rebuild for scaleability in the future.
- seabrookmx 7y ago
  > I'll be implementing the modern H.265 protocol used by videogame streaming companies Are you sure that's the right solution? Remote desktop is able to render sharp fonts because its sending a lot of desktop contextual information over the wire, as opposed to just doing a dump "capture the screen, encode it, and send" like the videogame streaming systems do. In a videogame, you can get away with small fringes on things (compression artifacts) but it would be quite jarring in your text editor. I've actually ran into this with the NX protocol (NoMachine) before, and it's one of the main reasons I went away from it.
  - GordonS 7y ago
    I agree with this, and it's exactly the reason why RDP is a vastly better experience than VNC. Using VNC on a LAN isn't great, but over WAN it's a truely miserable experience.

What tech is the remote desktop based on? VNC? Quite curious about how you keep the latency low enough that it to type in an editor.

by devxpy 7y ago

What tech is the remote desktop based on? VNC? Quite curious about how you keep the latency low enough that it to type in an editor.

greggman2 7y ago

Windows Remote Desktop has been usable or at least not completely unacceptable in the past. VNC though I've never seen it be acceptable for CAD so I'm curious too.

edunteman 7y ago
Windows Remote Desktop is the current tech in Booste, and is useable but not necessarily pleasant, I admit. Engineering priority #2, following multi-device-support, is to tackle the streaming challenge. I'm trying my best, as a solo founder, to not build out features until they're requested, so consider "Faster Streaming" to be requested!

emmelaich 7y ago

Apparently Citrix according to another comment. I thought it might have been https://www.spice-space.org/ https://www.spice-space.org/ which is GPL2. Amazon workspaces seems to use RDP

edunteman 7y ago
I encourage users to use their Windows RDP client for this version.
balakk 7y ago
Workspaces uses PCoIP AFAIK
- dillonmckay 7y ago
  I wish mobile OSs had an implementation of this or similar.

edunteman 7y ago

I actually have not engineered the streaming portion, so latency is the same as current VNC and RDP protocols. To get the product together as fast as possible (first line of code written three months ago), I actually did not reengineer the remote desktop protocol. In fact, the current product simply gives you the IP and password info to plug into your Windows Remote Desktop client app. Future plans are to integrate RDP into the Booste app, to make the experience seem more native. After that, I'll be implementing the modern H.265 protocol used by videogame streaming companies such as Vectordash and Nvidia GeForce Now.

mgamache 7y ago
h.265 will require hardware compression on the encode side (GPU) so you'll have to factor that into the cost.
- edunteman 7y ago
  For sure! Glad to have the tech insight. I already tether a GPU to the encode side for the 3D design apps, but I'll certainly need to rebuild for scaleability in the future.
seabrookmx 7y ago
> I'll be implementing the modern H.265 protocol used by videogame streaming companies Are you sure that's the right solution? Remote desktop is able to render sharp fonts because its sending a lot of desktop contextual information over the wire, as opposed to just doing a dump "capture the screen, encode it, and send" like the videogame streaming systems do. In a videogame, you can get away with small fringes on things (compression artifacts) but it would be quite jarring in your text editor. I've actually ran into this with the NX protocol (NoMachine) before, and it's one of the main reasons I went away from it.
- GordonS 7y ago
  I agree with this, and it's exactly the reason why RDP is a vastly better experience than VNC. Using VNC on a LAN isn't great, but over WAN it's a truely miserable experience.