Adobe discusses moving all of their applications to being delivered via a web browser.
What the ----?!! An image editor (further: a video editor!) is a complex thing, and people buy more advanced hardware so they don't have to wait 10 minutes whenever they use the paintbrush tool. One reason people use Photoshop is because it is fairly quick. Moving to the web would cripple that functionality. There would be nothing left!
Why, Adobe, why must you become the maker of bloatware only after winning over the marketplace?
For some time now, local computer power - hard disk capacity, write / read speeds, processor speeds, memory - has been growing magnitudes faster than bandwidth.
Adobe's applications work with huge amounts of data and require significant processing power to do so.
Therefore, according to them, the right thing to do is to take these applications and make them limited by bandwidth rather than local resources. Ingenious!
I'm all for splitting client and server systems (just so long as one can still install and access the server on the local machine), because it means some really good flexibility. Look at the X window system, for example: ssh, piping the X server stuff, results in the best remote desktop experience available. (All user interface settings from the local machine, including fonts and theme, are reflected in the application being run remotely. No ugly desktop; windows are drawn individually, handled by the local window manager). Sorry about that bracketted tangent... My point is that the problem here is not the server thing, or even the Internet thing (though time will tell whether they understand that they can't centralize this stuff to a single domain, as opposed to giving users the server software), but the web thing.
Why are all these developers worshipping the web as an application development platform? Except for simple things like word processors, it is terrible!
There are so many lines of bellowing anger I could run down to attempt to justify my hatred of web "standards" (at least in their current use), but I'll leave it at that.
Okay, having stuff like Photoshop a tad Internet-facing could enable neat functionality, such as a growing brushes library. However, that functionality does not, and should not, require a web browser to do. These things aren't special; with a bit of work, you can get the same online functionality, in a stand-alone application, as available in a web browser, with far more freedom in rendering and without the molasses speed of a web browser. Heck, it's easier in a stand-alone application, since Javascipt is ugly, CSS is inflexible (tables in professional looking web sites: count them! They are everywhere, even where they valiantly attempt to use exclusive CSS), and clients continue to behave in quirky, unpredictable manners. With a native application, we have one platform and only one platform: The operating system. Sure, hardware compatibility has to be dealt with, but that is getting increasingly less difficult than web browser compatibility, since the hardware manufacturers have some respect for why standards are important and because the OS deals with that for us.
...And please, Lord, smite anyone who gets the "bright" idea to create a web-based operating system that abstracts browser incompatibilities via a thick layer of Javascript and CSS. At this rate, it is bound to be attempted, but it would be disgusting if such a thing received even a moment's attention.
I've rambled enough. Sorry. Back to the topic: Adobe, web applications. Discuss :)
What the ----?!! An image editor (further: a video editor!) is a complex thing, and people buy more advanced hardware so they don't have to wait 10 minutes whenever they use the paintbrush tool. One reason people use Photoshop is because it is fairly quick. Moving to the web would cripple that functionality. There would be nothing left!
Why, Adobe, why must you become the maker of bloatware only after winning over the marketplace?
For some time now, local computer power - hard disk capacity, write / read speeds, processor speeds, memory - has been growing magnitudes faster than bandwidth.
Adobe's applications work with huge amounts of data and require significant processing power to do so.
Therefore, according to them, the right thing to do is to take these applications and make them limited by bandwidth rather than local resources. Ingenious!
I'm all for splitting client and server systems (just so long as one can still install and access the server on the local machine), because it means some really good flexibility. Look at the X window system, for example: ssh, piping the X server stuff, results in the best remote desktop experience available. (All user interface settings from the local machine, including fonts and theme, are reflected in the application being run remotely. No ugly desktop; windows are drawn individually, handled by the local window manager). Sorry about that bracketted tangent... My point is that the problem here is not the server thing, or even the Internet thing (though time will tell whether they understand that they can't centralize this stuff to a single domain, as opposed to giving users the server software), but the web thing.
Why are all these developers worshipping the web as an application development platform? Except for simple things like word processors, it is terrible!
There are so many lines of bellowing anger I could run down to attempt to justify my hatred of web "standards" (at least in their current use), but I'll leave it at that.
Okay, having stuff like Photoshop a tad Internet-facing could enable neat functionality, such as a growing brushes library. However, that functionality does not, and should not, require a web browser to do. These things aren't special; with a bit of work, you can get the same online functionality, in a stand-alone application, as available in a web browser, with far more freedom in rendering and without the molasses speed of a web browser. Heck, it's easier in a stand-alone application, since Javascipt is ugly, CSS is inflexible (tables in professional looking web sites: count them! They are everywhere, even where they valiantly attempt to use exclusive CSS), and clients continue to behave in quirky, unpredictable manners. With a native application, we have one platform and only one platform: The operating system. Sure, hardware compatibility has to be dealt with, but that is getting increasingly less difficult than web browser compatibility, since the hardware manufacturers have some respect for why standards are important and because the OS deals with that for us.
...And please, Lord, smite anyone who gets the "bright" idea to create a web-based operating system that abstracts browser incompatibilities via a thick layer of Javascript and CSS. At this rate, it is bound to be attempted, but it would be disgusting if such a thing received even a moment's attention.
I've rambled enough. Sorry. Back to the topic: Adobe, web applications. Discuss :)