> Apollo alpha is out:
> Running the samples... Looks good.
Someone shoved this book
in my bag at SD West. I've read the first chapter and it finally dawned (:idea:) at me what they are doing.
So, by this point, you may be saying to yourself, â€œGee, Apollo sure sounds great!
Why would anyone ever want to deploy an application to the browser again? Is Apollo the end of web applications within the browser?â€
Letâ€™s repeat that again: no.
Apollo solves most of the problems with deploying web applications via the browser.
However, there are still advantages to deploying applications via the browser. The fact that there are so many web applications despite the disadvantages discussed earlier is a testament to the advantages of running within the browser. When those advantages outweigh the disadvantages, developers will still deploy their applications via the web browser.
But it is not necessarily an either/or question. Because Apollo applications are built using web technologies, the application that you deploy via the web browser can be quickly turned into an Apollo application. You can have a web-based version that provides the browser-based functionality, and then also have an Apollo-based version that takes advantage of running on the desktop. Both versions could leverage the same technologies, languages, and code base.
Apollo applications complement web applications. They do not replace them.
It seems that WebWidget GUI is still a go, although with Apollo compatibility kept in mind.