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?
If graphics artist types can't make the kind of pointless crap that they do now with Flash, we won't see uptake of HTML 5.
How we know is more important than what we know.
Just because I can embed video and sound doesn't make my HTML pages the equivalent of flash. More importantly, Microsoft has "announced" intension to support HTML 5, but there's exactly zero movement so far from the market leader, and a long history of similar unfulfilled promises. Until Microsoft says HTML 5 is the next big thing, it isn't. Sorry, I know it sucks.
Celebrate failure, and then learn from it - Nolan Bushnell
Flash, Silverlight, and JavaFX all have major vendor tooling support to help coding, developing, deploying on these platforms easy. I don't know of any tools in existence or in development that can beat the solutions offered by these vendors. Adobe might be willing to do that in the past, but they own Macromedia (flash) so I don't know if they will step up. In short, unless the tools are there, it will not see major adoption.
I've recently embarked upon a hobby project where I'm only targeting the latest browsers, excluding IE8.
Not until now have I realized how much we web developers are hampered by IE. Canvas and Javascript are a highly capable platform for interactive graphics, and it works across browsers and operating systems without issue. Chromium on Linux for example, incomplete as it is, works with canvas out of the box (not to mention about 10 times faster than FF in executing Javascript).
The ability to create web pages quickly, using convenient CSS2 and 3 rules, the ability to use piles and piles of Javascript without worry, the ability to have everything just work across my target browsers, it's utterly amazing. If we weren't stuck in this damn backwater due to having to support IE, the web would be a far more compelling platform.
I absolutely cannot wait for the day when HTML5 and CSS3 are widely supported and adopted, but will that day ever come? Surely Microsoft realizes, as I have, how much potential is here, and I don't doubt that some of the higher ups would hold IE back so that developers are forced to use their plugins in order to deliver their content.
For those projects that don't care about IE support, HTML5 canvas/video/audio is a fantastic leap forward for the web. For the rest, business as usual for some time to come I'm afraid.
I'm sorry but I just can't stand developing in Javascript. Javascript is hands down the most arcane language I find myself developing in. At this point being locked into a language like Javascript by the standards community seems much more restrictive than what the proprietary plug-ins are offering. Programming in both Silverlight and Flex has been a liberating experience for me. When using Silverlight or Flex I'm able to focus on creating an application that satisfies my customer's needs; instead of focusing on the black magic tricks that are so often required when using Javascript and HTML. At the end of the day it's so obvious that HTML and Javascript were not intended for serious application development. Not only do Silverlight and Flex offer better programming models they also offer rich support for databinding, and that has simplified so many of my applications. So unless HTML 5 comes packaged with a better programming language and data binding you can count me out.
The fundamental issue with the new RIA standards is the lack the of authoring tools. I have got a number of graphically-inclined friends who are never going to write something with HTML5 mainly because there are no tools out there (yet) which come even close what the Adobe authoring tools can do.
Recently, I sat with one of my friends (who's a decent artist) and played around with Processing 1.0. After several minutes of hard work, it just became abundantly clear that visual thinkers have a lot of trouble expressing what they want algorithmically. The experience was repeated the next time, when he was playing around with chucK (yeah, he's a music dude too).
The graphic artist folks will have a lot of trouble using the HTML 5 authoring tools currently available, especially if they're confined to use HTML Canvas programmatically. I've easily gotten upto speed with canvas, but I'm a programmer with no artistic pretensions.
Real adoption of HTML5 - canvas and video & all, will need easy ways to author media ... not write code.
Quidquid latine dictum sit, altum videtur
The big problem with HTML5/JavaScript/CSS is that each browser has quirky behaviours that need to be tested. Even if Internet Explorer no longer existed, developers would have to test against Firefox, Safari, Chrome and maybe Opera. An example of a quirk is Safari not recognizing table element widths in percentages. A Flash developer tests against one Flash runtime, same with a Silverlight developer and a JavaFX developer.
Adobe released a beta of a multiple browser runtime testing tool, but it's apparently very flawed.
So until the above problems are solved, many RIA developers will simply use Flex, Silverlight or JavaFX, instead of coding for a hodge-podge of different browsers.
This space left intentionally blank.
Microsoft might be part of the w3 organization, but none of their browsers support any of the HTML5 specs, i dont call that being involved, instead they have specifically decided not to support these standards, and try to slow down, and break apart the web.
For the past two years, I've been telling everyone the new browser war is between IE and WebKit. WebKit has become the default platform for the mobile browser market (iPhone using Safari and Android and Palm using their version). One of the big reasons Apple started WebKit was to keep the browsing platform out of the hands of a single vendor. It's not that Apple doesn't like proprietary technology. It's that they don't like proprietary technology that they depend upon and don't control.
The battle for HTML 5 vs. Silverlight vs. Flash will be on the mobile platform. It's easy for Silverlight and Adobe to create a desktop application that work with 90% of the desktops (and a bit more work to get another 9%). However, the world is changing. Adobe and Microsoft can't create Silverlight and Flash clients for every single possible mobile platform. The trick is to get enough HTML 5 clients out there that it'll be worth it for developers to learn HTML 5. If enough developers pick up HTML 5, companies will make IDEs for HTML 5.
If that happens, Flash and Silverlight will go away. The other possibility is that Apple will buy Adobe and open source Flash. Apple loves open source standards because it means that they'll be able to sell all the neat gadgets that work with these standards.
And yet those tools produce more crap code than Microsoft had market share for its Windows operating system and Internet Explorer browser in the first few years of this decade.
Seriously - there's a huge problem when someone can create a Web page with a WISIWYG editor that breaks when a new browser, browser version or rendering engine comes out and is generally inaccessible to people with disabilities while leaving search engines guessing which content is the most important; yet I can create the exact same page by hand using nothing more than a plain text editor and a decent graphics program (like Paint Shop Pro or Photoshop Elements) that works just as well in Internet Explorer 5, IE6, IE7, IE8, Firefox 2, Firefox 3, Opera, Safari, Chrome and other browsers without having to update them whenever a new browser, browser version or layout engine is released - without hacks about 90% of the time for any browser. And that's just for GUI capable desktop clients.
While using only 25% of the code the WYSIWYG editor barfs up, making the site accessible to everyone (not just the disabled), search engine friendly, and able to support up to three times as many people due to lower code weights, fewer HTTP requests needed with every page view, and optimized images (CSS sprites anyone?) - and that's just off the top of my head.
If I can learn how to do that, anybody can. And my high school counselors (not to mention my family and their friends) thought I would never amount to anything.
Major League Baseball Advanced Media totally botched the transition not once, but twice. When switching from Flash to Silverlight last year their new Silverlight-based streaming player didn't work, leaving paying customers without service for days. This year they decided to switched back to a Flash-based player ON OPENING DAY. Unfortunately, the new player doesn't work either, and in many ways was worse than the silverlight player, requiring additional installation plugins for HD capabilities, and left these same paying customers without the opening day experience they're paying for two years in a row.
New York Times Reader was a different case. It worked fairly well, but NYT got thoroughly flamed for introducing the reader for windows only, basing it on WPF's FlowDocument capabilities which aren't available for the Mac. Similar text features are eventually going to make it into Silverlight, but things like Printing are a much higher priority for the SL guys. The silverlight version of the reader used a complicated templating system rather than true adaptive text layout. Adobe's Text Layout Framework may not have been the first to market, but that + Flex + AIR are the first to bring it to a wider audience and may ultimately resonate more.
Also I'm sure politics played a prevalent role in both cases, especially in the case of NYT where the Mac User's vitriol for anything microsoft played out.
MLB 2008
http://www.pcworld.com/article/144035/mlbs_web_video_strikes_out_on_opening_day.html
MLB 2009
http://www.huffingtonpost.com/robert-j-elisberg/major-league-baseball-str_b_185158.html
NYT:
http://www.itwriting.com/blog/1424-new-york-times-switches-from-wpfsilverlight-to-flash-for-reader-2.html