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?

Comments

It's the tools stupid

[QuantumG]

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.

Re:It's the tools stupid

[Anonymous Coward]

The irony is that the most popular WYSIWYG editors are produced by Adobe and Microsoft.

Re:It's the tools stupid

[ink]

Amen. I wish more developers would take the time to understand this point. Without an analog to Adobe Illustrator, Adobe Photoshop and Adobe Flash (vector animator/tweening) -- no other technology will succeed. HTML5 is a great _engine_, but that's all it is until we have the tooling to make it actually useful.

Re:It's the tools stupid

[StreetStealth]

What you're not considering are all the other Flash-based sites that don't trade in pointless crap -- the far more subtle ones where you have to take a peek at the context menu just to be sure they aren't actually using some particularly clever JavaScript.

These are the sites that use but don't abuse Flash, and are the best candidates for HTML 5's more lightweight environment. If the designers and developers of these sites can be convinced it's worth migrating from Flash for the decreased overhead, they just might.

Re:It's the tools stupid

[Tronster]

Microsoft wins market share, not by innovating, but by making a product, and quickly iterating up-to and past the leader.

Adobe has more baggage to deal with (e.g., http://blogs.adobe.com/rgalvan/2009/06/feature_feedback.html ) which hurts the speed they can push ahead with new features. I've tried Silverlight 1 and 2; both show promise but neither seemed as mature as Flash CS3. Now CS4 is out as-is Silverlight 3. Silverlight 3 compared to 2 offers many times newer features than what Flash CS4 offered over CS3.

For example, I'd love an integrated code editor in Flash with decent editing, syntax highlighting, and intellisense capabilities; I've been waiting for this since MX2004. Silverlight 3 now has a built-in code editor, I wonder how well it stacks up to what Adobe offers.

Overall I'm glad Silverlight exists as it will push Adobe to keep making Flash a better technology, but historically Microsoft has come out on top. It took Microsoft 6 years from IE1.0 to make this happen in the browser marked ( http://en.wikipedia.org/wiki/Usage_share_of_web_browsers ) With 3D it took Microsoft until 6 years, from DirectX 1.0 to DirectX 8.1, to overtake OpenGL in the AAA PC gaming market.

Unless there is a shake-up in Microsoft I predict it will happen with this RIA tech too.

Re:It's the tools stupid

[Fallen Seraph]

Independence from Adobe for one. Right now, without Flash, Youtube does not work, period, end of story. That's why they're experimenting with the HTML5 video tag, so that Adobe won't be able to screw them over one day if they feel like it. Granted the likelihood of that happening is slim to none, the potential threat is enough for them to try as hard as possible to push for open standards. This is exemplified by things like the mobile web. While Opera pushes their mobile browser hard, mobile browsers as a whole are limited by Adobe's watered down FlashLite deployments, which makes rich media for mobile browsers nearly impossible using anything but javascript (which is still limited).

Not to mention the fact that it enhances the user experience. If you can just get a browser, with no plugins required, that's much easier for users to deal with.

And on a final note, have most of the people arguing that Flash is "easier for designers to use" actually used Flash? Doing anything really interesting in Flash requires using Actionscript, and Actionscript 2 is basically a javascript clone, while Actionscript 3 is more similar to Java. I learned actionscript 2 before I learned javascript, and the total time to go from one to the other was about 10 minutes (how long it took to learn the new constants, global variables, and proper DOM manipulation).

The fact is, if the web is to continue to grow, it MUST shirk Adobe and Microsoft's proprietary plugins for open standards. Not only do they often run better (Flash can be amazingly bloated, just look at Hulu's standalone Adobe Air app), but they give us more options and possibilities as well.

Re:It's the tools stupid

[cheesybagel]

Microsoft has tried to replace the PDF format several times in the past and failed.

Total nonsense

[WaywardGeek]

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.

Need good tools

[poached]

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.

Yeah, but javascript sucks

[Virus Hunter]

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.

Re:Yeah, but javascript sucks

[acidrainx]

I was ready to jump on you when I read the title of your post, but you're right, mostly. JavaScript is actually a really nice language to develop in (for small projects). With features such as lambdas, closures, and functions as first class objects, you can write some very elegant solutions with very little code.

Even with those features it's still stuck in the dark ages when compared to other modern languages. Prototypal inheritance, while cool, doesn't really offer the power that classical inheritance gives you when you're creating large systems. There's no such thing as super in prototypal inheritance, which gets annoying after a while.

Lately I've been looking into Flex and ActionScript 3. AS3 is basically what EcmaScript 4 was going to be before Microsoft derailed it. It's basically Java with a different syntax, a few extra features (lambdas, closures, namespaces), and no equivalent to abstract. It's really nice.

While I'm all for HTML5 and open standards, I highly doubt that it will ever be able to keep up with proprietary solutions like Flex. There's always going to be that big asshole in the corner who refuses to keep his browser up to date with everyone else. I've written large programs in JavaScript and its just far too stressful trying to keep IE-compliance. Until Microsoft or IE are dead and buried, I'm going to have more fun writing Flex apps that run on all browsers and all platforms without any platform specific code.

well...

[evil_marty]

this is the beginning of the no-plugins trend and I for one think its about time. Sure some 98% of people have flash installed, silverlight much much less and java (well I tend to steer away from that as much as possible, besides when was the last time anyone ran an applet these days?) but the problem we are seeing is that single vendors take there time to migrate to other platforms, and usually then they lack features and what nots. Look at flash, it isn't even available for the iphone and it's linux support is very limited (alpha still?) not to mention lacking 64bit in windows, fucking windows! If flash was an open platform then more external resources can be used to address these situations but then this is where html5 goes one step further, instead of making it a plugin for everyone to download why not just make it part of the browser and save the hassle.

Developers, developers ... and authoring tools

[Gopal.V]

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.

Microsoft?

[asdfndsagse]

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.

Re:Adobe brought this on themselves

[derGoldstein]

As an aside: Does anyone remember how they pushed SVG before they bought out Macromedia? They even made a decent player, which you can still get here. Notice the first line on the page: "Please note that Adobe has announced that it will discontinue support for Adobe SVG Viewer on January 1, 2009."... Who needs SVG after you own Flash?

Screw Flash. Screw Acrobat. Screw Silverlight. On the web, the most puritan Free Software advocates are right: If it's proprietary, don't download. Don't install. You've just giving them the power to take away your choices.

Re:We independent developers decide that ...

[shutdown -p now]

It could be done with PHP because replacing server software doesn't affects clients; in particular, it does not require them to install new plugins and/or change their browser.

Client-side, it's a very different kettle of fish. Silverlight can fight Flash by being bundled with the OS (or installed wia WU); JavaFX can fight it by being bundled with JRE (or installed when JRE is auto-updated). I don't see any similar opportunity for HTML5.

Re:HTML5, with canvas, is fantastic

[derGoldstein]

I'm actually staring at the screen and trying to think of what to "say". Have you just met Microsoft? They've had .Net code running on BSD since ~2002, and I'm *not* talking about Mono. They've released plenty of code that runs "on the competition", while attacking both from the legal *and* the PR fronts. It's all a messed up game for them, they're stalling for as long as they can. They'll help you along with your science project and then sue you for using their patents in it. If we haven't learned this by now, I suppose we never will.

You're right - the tools are stupid.

[Dan Schulz]

In this day and age, you don't need to know good html in order to make a webpage. We have WYSIWYG editors. So I don't see why we couldn't have an editor for the canvas tag, that would provide artists with a point and click interface like flash does.

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.