Also, anyone else notice this amusing note at the bottom of the FAQ:
Please post your issues to [Insert Forum Link]
Because there are a lot of things Adobe might not care about as much as you'd like- but color accuracy is one of the things they care about A LOT.
(I spent a summer working in an art computing lab, nearly every minute of which was spent managing color accuracy)
Photoshop seems like one of the most difficult programs to work via VNC.
I think it's actually the opposite. Usually only a small amount of the screen is changing, so response is fast. For full-screen or complicated effects they can provide more CPU horsepower than your average laptop, so the operation may actually complete faster, even if screen redraw takes more time.FWIW I've used Photoshop over Remote Desktop in the past and with a good connection it feels perfectly usable. There's a little input lag which is only noticeable with sweeping brush effects, not UI interactions, and like I say large area screen redraw (e.g. scrolling) suffers. There's no visible compression or artifacts and I don't see why color correction would be an issue.
This would be a huge issue for the professional market. But it appears that they are targeting education with this first (or maybe just that market). Color precision is likely not the highest of priorities.
It could mean that half of the screen is changing with every step of the slider, and you want exact color, immediately.
For one, doing client-side color correction (for example with WebGL) is technically possible. It's probably not in this solution, but let's not use words like "impossible" unless they're actually impossible.
But more importantly, I think you're just complaining about latency, but then you're using the phrase "impossible."
EDIT: I thought you were talking about gamma correction and the color space of the display, where the program running on the server wouldn't know about the gamma and color characteristics of the monitor on your current browser. Thus, "monitor settings." But no, you're just worried in general about whole-screen fill rate latency. Again, I think using terms like "impossible" is hyperbole. It will be fine for some users, and not for others.
I actually do, but i don't know whether it's public, so i don't talk about it.
However, i'll point out that Google already has something called Chrome Remote Desktop that already does streaming desktops.
Also on the bottom of that FAQ it says "Please post your issues to [Insert Forum Link]" heh.
I can imagine, given experience with VNC or even some crappy RDP implementations, it sounds like it would be terrible. But those are pretty old and bad technologies for remote desktop usage, with known issues. You can do better.
I'm sure there are situations where the experience is not ideal.
But remember that you are talking about people using chromebooks here. They are computers basically built with the expectation that you have good internet, and they are targeting the education market here.
I would point out that neither Adobe, nor Google, would want people in the education market (one of Adobe's prime targets) to have a crappy experience with Photoshop, as it would be really bad for both parties (if Google makes a bad first impression with chromebooks, people write them off and never try them again. If Adobe makes a bad impression with photoshop, people won't pay hundreds later on to buy it).
So one would imagine they would not release a terrible experience :)
Sadly I don't think I've ever been in an educational institution where the wifi was particularly reliable. Wired ethernet yes, so a computer-lab setup can work well with remote-desktop type stuff. But that's getting increasingly old-fashioned, and everyone connects on wifi now, which seems to often not be up to the task. We have some huge pipe at the university I work at, and my wired office connection is great, but the wifi? Frequent dropouts and latency spikes, especially if a bunch of people in one room are doing network-intensive stuff. I can believe our IT infrastructure isn't among the best, but it's not the only place I've had that trouble either.
As an Australian, I fear this is yet another one of those things we won't be able to use on our spotty 250KB/s connections.
The processing is local, that is for sure.
Their FAQ[0] contains some more information, but still does not explain everything. They say "however, instead of being installed on your local machine, it is running in a virtualized environment so can be accessed from any Chrome browser or Chromebook. Because this version of Photoshop is running in a virtualized environment, you open, save, export and recover files from/to your Google Drive rather than your local file share."
It would seem that they are indeed streaming the video (VNC-style). More over, space requirement is only 350MB (Photoshop is normally much bigger), and there's also this:
"If network connectivity is lost, you will need to launch a new session. A recovery folder called ‘Photoshop Recovery’ will be created in the root of your Google drive. To recover files, simply double click to open a file."
Overall, this doesn't sound good at all. If they are streaming screen "video", color correction and pixel-level precision in design is going to be tough. Photoshop seems like one of the most difficult programs to work via VNC.
[0]: http://edex.adobe.com/projectphotoshopstreaming/faq