Having used both Citrix and Mighty, it’s clear Mighty cared about latency in a way that Citrix doesn’t (or, more generously, is out of control of Citrix since they don’t own the end-to-end system)
I think it's more of a hybrid approach, the web renderer was running in the cloud, the ui was native and local.
I beleve Citrix is mostly a standard VNC type product where everything is rendered on a server and streamed. I was envisaging a toolkit to enable you to build an app where parts of it run in cloud, parts of it locally.
Think of a 3D cad tool, the ui could be all local, but the rendering and compute is in the cloud. Or a 3d physics based ray tracing app, you could do the 3d wire frame locally, but have the real-time ray tracing happening on a very large server.
On top of that, by have a cloud based state, it's only one step away from marking that state shared with other users to enable collaboration.
You're misinformed. Citrix has plugins for managing aspects of GUI rendering, video/audio playback and GPU pipelines local on the client, which are a key part of the "secret sauce" behind their success in industry.[1] This is a product which is being used today for remote CAD/CAM workflows in the largest firms, whereas afaict applications of Mighty's product to this problem sphere is nothing but idle fantasy by HN posters?
