|
|
|
|
|
by InclinedPlane
5378 days ago
|
|
"It would actually be stupid implementing Photoshop in the browser." You say that now... In truth I don't think there's a fundamental reason why that's such a bad idea, and I think it will happen in the coming years. JS compilation is getting better and better, eventually it'll reach the theoretical limits, which is to run more or less as fast as client-side C. Similarly, web standards are improving at an amazing rate, given the development base and momentum behind web applications (which are growing to be as big a business as any platform) eventually we're likely to end up with all the bits and pieces for supporting web apps (UI elements, frameworks, etc.) at a level matching that of desktop development. At some point it's not only possible but indeed very likely that a photoshop web app will be built. But by then it probably won't seem like a crazy idea. |
|
This is an important difference -- Moore's law is still applied -- but image resolutions are getting bigger and bigger, algorithms get more complicated and more fancy, people also want to be more and more productive.
What I'm saying is that image retouching for professionals needs every CPU cycle you can spare + screen real estate + really good integration with input devices.
I'm not seeing the browser (which stagnated for years), as a powerful enough medium for that, unless you can make Javascript as-fast-as-C without sacrificing too much RAM (since you need that too) and unless you provide lower-level access to hardware (OpenGL ES is a good start, but you need more).
Now surely, if Photoshop can't be built in the browser, that doesn't mean something less powerful will be less useful. But it won't be Photoshop.