Originally Posted by spliff monkey
I am imagining it and it sounds awful. Not only do I have to wait for FCP to load but now I have to wait for it to download first? and I have to have the internet wherever I go? what if I'm in the field? what a waste.
No, you visit the URL to get the latest version. When they make an update, you don't have to think about downloading a package release, it just adjusts the code as needed. Say that there's a bug in one very small part of the app, visiting the URL will get the update without thinking about it.
The system would cache the compiled binary or encrypted source so online access is not needed. It also execute locally and edits/stores content locally. Chrome OS uses the cloud and I agree with you that's not a good solution. This would be the next iteration of webapps.
Websites use the latter languages because they have rapid application development and testing times, the former are used for native apps due to performance and code security. If you had something to give you both then you end up with webapps that can be distributed from a URL that run locally, compile and run as fast as any website loads but that execute as fast as a native app.
Code security is essential for proprietary products but that's why it needs to be protected at the OS level. Apple can feed it straight into the core of the OS as encrypted code and compile it on-the-fly. This also dynamically optimizes code for every single platform the best way it can.
Originally Posted by Ecphorizer
On the third hand, this might bring about a lessening of software piracy - good news for consumers with (hopefully) associated price drops.
Yes, exactly because if they feed the code from a URL in an encrypted form then it's way harder to take that encrypted code and recompile it on another platform. They'd have to actually rip out the compiled binaries from their locations and reinsert them or hack the OS and gain access to the codebase somehow. It could be disastrous if the source code leaked onto the web in some ways but y'know, people are stealing binaries all the time so I don't think it would be that big of a deal and visiting the URL by accident would detect the modification and wipe it out.
It makes the OS more streamlined too. Right now, they bundle all sorts of apps on the OS like iWork with as many GBs of templates. Same with iPhoto. Instead, they can just have URL links in the dock. If you actually use a template, click on the template and it downloads. No need to waste space for stuff you never use like with the printer drivers.
Instead of having 40 templates you don't like and bundle all 1GB of them, have an online selection of 400 and just download the one you pick. It's only going to be 5MB or so each.
Not to mention, you can setup your work machine like your home machine by emailing yourself a set of URLs and just visit them at work with your access details. It will install all the apps you need.
Originally Posted by ThePixelDoc
Adobe is testing the waters with this "module" type of approach, by hooking in Flash to Photoshop Extensions (see Kuler, PainterWheel, additional Live Services, etc.), as well as Air. However, they are struggling dearly with Flash, and still haven't given in to the fact that they will almost without a doubt have to recode that piece of their puzzle from scratch.
Yeah, it's funny how it took an about turn. The big app developers are now realizing that the codebases are unwieldy and struggle to add anything interesting in their products to justify the upgrades and anything they do add, it's the little core additions. Like content-aware modifications in CS5. That is one of the most useful things I've ever seen and yet it's one little algorithm in a codebase with millions of lines of code.
Apple likes innovation and modular components are the best way to deliver them because a developer who wants to make an algorithm like the content-aware code doesn't have to concern himself with how to make the CS5 app to run it. That's someone else's problem. This is one flaw to the modular approach - it's relying on other people to pick up rest of the pieces and drive it in a direction you are happy with. With monolithic apps, one company has absolute control.
The good thing about modularity is that it opens up the development industry to anyone and everyone to make a profit. It needs this new language though so it all works together.