Comments on: Flash, HTML, Ajax: Which will win the Web app war?
Web applications are getting richer and more widespread, but it's unclear which of several competing technologies will power them.
Web applications are getting richer and more widespread, but it's unclear which of several competing technologies will power them.
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
Your destination for the latest news on enterprise-level information technology, from chip research and server design to software issues including programming, open source and patents.
Add this feed to your online news reader
Read a book, called "Snowcrash", or simply watch a sci-fi film like lawnmower man.
Of course this article has little to no meaning because it attempts to compare Apples to Oranges, and to compound it's meaningless, illustrates the authors lack of understanding in the field itself.
As RIAs (rich internet applications) become an assumption when building a new website (instead of a conscious choice to differentiate) there will likely be a "winner' who establishes a dominant mindshare of web developers. It may be a single vendor (like Adobe or MSFT) or it may be the open web (with supporters like Yahoo, Google, & Apple). This doesn't mean the others just disappear, it just means that they become secondary players.
My money is on Ajax because of it's widespread support of well-established standards. The biggest challenge has been that it required ninja-level JavaScript knowledge to build webapps comparable to Flex/Silverlight. However, with the introduction of JavaScript/AJAX frameworks like Appcelerator, DOJO, Prototype, JQuery, Scriptaculous, ExtJS, etc. this is no longer the case (thank god!). The introduction of Firebug has been an incredible improvement as well for web developers.
-Quin'
VP, Community
Appcelerator
http://www.appcelerator.com
As with Flash a developer needs to proxy calls inside the SWF file via External Interface API, which further illustrates how closed source the SWF format really is.
In Silverlight, this is not required, in fact we've provided access both inside Silverlight via the HtmlWindow Class and outside via the getElementById('YourSilverlightControl').Content API. Which allows folks the ability to reach into the Silverlight runtime without an External Interface API / Firewall.
Further, you are not restricted to just .NET, using the DLR folks have the ability to pick and choose which language they would like to use. If you will, people have the ability to add languages they wish to Silverlight (ie so far IronRuby, IronJava etc).
-
Scott Barnes
Rich Platforms Product Manager
Microsoft.
the fight really is about whether html should build in the functionality that flash was providing all these years or not
flash was never intended to be an application platform by itself..
however AIR a not so old launch from Adobe is a disruptive technogy for the web..
the wear really is between conventional browser technology .. (yes all of it) and the new AIR platform
now go figure
also keep an eye at
http://defuturo.blogspot.com/
- by gmclean0402 August 13, 2008 4:53 AM PDT
- Who cares which on-line technology will dominate. If your apps are all on-line, when the power goes out, the server goes down, Time Warner/Roadrunner goes out and all you have left is a MacBook Pro with a full battery, you will fall in love with MS Office all over again.
- Like this Reply to this comment
-
Showing 2 of 2 pages (43 Comments)