Slashdot Mirror
HTML 5 Takes Aim At Flash and Silverlight
snydeq writes "While Adobe, Microsoft, and Sun duke it out with proprietary technologies for implementing multimedia on the Web, HTML 5 has the potential to eat these vendors' lunches, offering Web experiences based on an industry standard. In fact, one expressed goal of the standard is to move the Web away from proprietary technologies such as Flash, Silverlight, and JavaFX. 'It would be a terrible step backward if humanity's major development platform [the Web] was controlled by a single vendor the way that previous platforms such as Windows have been,' says HTML 5 co-editor Ian Hickson, a Google employee. But whether HTML 5 and its Canvas technology will displace proprietary plug-ins 'really depends on what developers do,' says Firefox technical lead Vlad Vukicevic. It also depends on Microsoft, the only company involved in the HTML 5 effort that is both a browser developer and an RIA tool developer. 'That's a big elephant in the room for them because you can imagine the Silverlight team [whose] whole existence is to add [this] functionality in. [But] if Internet Explorer puts it already in there, why do we have Silverlight?' asks Mozilla's Dion Almaer." The RIA guys are quoted as saying they're not worried, because HTML 5 + CSS 3 is 10 years out. Are they just whistling in the dark?
I think you have a very unusual definition of "app". If an entire app exists and you just need to embed it with 2 lines, you did not write an app, you used an existing one. If I make my own bash script to launch Firefox, did I write a web browser app?
Sam ty sig.
In addition to the wonderful video, audio and other enhancements of HTML 5 let's also get Native Clients for powerful apps now please!
Native Client: Using Native Code to Build Compute Intensive Web Applications
Client Track - Brad Chen, David Sehr, Nicholas Fullagar Some applications require high-performance client-side computation. Native Client is a technology for running native code in web applications, with the goal of maintaining the browser neutrality, OS portability, and safety that people expect from web apps. This talk will give a brief overview of the architecture of Native Client. We'll then look at some specific example applications as well as strategies for how to use native code to handle compute intensive tasks within web applications using SRPC, Shared Memory and NPAPI. Native Client.
Native Client will enable me (or you) to have web pages running MY (or your) OWN choice of programming language including a mix of languages as I (you) see fit. True freedom of choice, power and higher speed. Desktop powered apps can finally come to the desktop no matter what language they are written in!