I develop desktop apps that are run exclusively virtualized, and don't really have to deal with either set of problems. From a developer perspective I'd say it's a pretty sweet spot, as you get the best of both worlds to some extent.
Granted, communicating with any type of hardware on the users machine is a major challenge. We've had to spend significant effort just troubleshooting printer issues. If you need low latency, virtualization is likely a non-starter.
The upshot is that the latency between our apps and the application server/database (hosted in the same domain) is much lower than for a conventional web app.
Comments
I develop desktop apps that are run exclusively virtualized, and don't really have to deal with either set of problems. From a developer perspective I'd say it's a pretty sweet spot, as you get the best of both worlds to some extent.
That's an interesting point, but I'm not sure how well this works for e.g. communication with low latency harware?
Granted, communicating with any type of hardware on the users machine is a major challenge. We've had to spend significant effort just troubleshooting printer issues. If you need low latency, virtualization is likely a non-starter.
The upshot is that the latency between our apps and the application server/database (hosted in the same domain) is much lower than for a conventional web app.