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
...which is #52 here talked about JavaFX and its prospects for a bit. One of the guys had just gotten back from JavaOne and was talking about the vibe he was getting about JavaFX. Larry Ellison apparently commented favorably about it, so, whatever that means.
RIA Weekly is a good podcast - Michael Cote is a savvy guy and he always has good discussions with his cohosts/interviewees. AAAA+ would buy again.
The Army reading list
Microsoft simply won't add HtML 5 audio//video tags to IE.
Dump Flash and Silverlight into the dust bin of bit history along with the YouTube master control! Onward!
How about adopting Chromes Native Code Binary API plugins for all the browsers while we're at it? Let's get it so that we can auto download plugins written in languages other than that icky JavaScript gooicky stuff.
Get on with it guys! The web browser is still just so much as a dumb terminal spitting screens to a central server master control program!
Let the independent distributed revolution begin!
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.
When the browsers support html 5, people can start making content for it. The whole reason for flash and siverlight are the failures of the old html (which still shines despite having all this stuff bolted-on over the years to keep up)
If HTML 5 means just another bunch of tags with another bunch of CSS descripters and a set of scripts in a different language bolted-on to make it do stuff, along with spotty browser support, I suspect the one-stop shops of UI with scripting that flash and sliverlight provide will have a long future.
The RIA guys are quoted as saying they're not worried, because HTML 5 + CSS 3 is 10 years out.
If this is the case, how far behind will the browsers be in supporting the standards?
No incumbents, not no where, not no how.
Vote them out every term.
but it won't work in IE until the point's moot. Remember kids, it's not done until Lotus 1-2-3 won't run!
HTML5 is incredibly awesome. I've been building some apps that run only in safari and the things you can do in so very little code make Flash and Silverlight look like anemic. What people don't realize is that HTML5 means tools to author HTML5 in HTML5. I've done a simple Object Oriented Javascript programming interface that currently only runs in Safari4 (only one with sufficient HTML5 support), and it is amazing what you can get done in 500 lines of code. Using the framework at http://www.dloh.org/ I built a graphing app by adding 2 lines of Javascript. A simple movie player is 5 lines of javascript. It takes stupidly little code to make compelling apps using the right tools and HTML5. Furthermore, more and more phones are supporting the WebKit framework. Qualcomm is recruiting a team to port webkit, so we'll soon see it on Brew phones. Iphone runs it. Android phones run it. And even if you run Opera, once again you're getting decent HTML5 support on your phone. This is game changing technology because it runs on the devices that most of the 6 billion people on the planet actually use.
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.
What's RIA? Is it like the RIAA but without the A at the end? What's next then, MPA? BS?
Had Adobe not steadfastly refused to put any end user controls or setting in Flash no one would have bothered to develop alternatives.
But because they wanted to cater to the jumping monkey segment of the web advertising world, they stonewalled every request for end-user controls, such as no looping, no animation, no sound, etc.
Besides the fact that it is bloatware, its just end user un-friendly.
In order to control Flash, you needed to kill Flash and millions of web browsers would like to do exactly that.
Being an open standard HTML5 is open for development of end-user controls, such as animate only while cursor hovers, sound off till I say so, etc.
Bring on HTML5.
This is a market Adobe deserves to lose.
Sig Battery depleted. Reverting to safe mode.
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.
So it's no surprise sites turn to Flex, Silverlight or JavaFX. While they are proprietary technologies they do generally work as claimed and even in a cross-browser and cross-platform manner. It's also easy for sites to persuade people to download & install the plugins without the trauma of upgrading or replacing their browser since the browser will help them do it.
Therefore I don't see HTML 5 supplanting RIA plugins for a very long time if ever. It would require decent support by all leading browsers. In some instances such as Internet Explorer, there is even a very major conflict of interest which makes it unlikely to happen. Aside from these hurdles, another major issue are AJAX toolkits and development environments. Frankly developing AJAX stinks for all sorts of reasons, and I don't see that situation changing much either.
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
What I hear is that "we need an open standard on video that is not controlled by one [proprietary] company."
But when it comes to Linux and where system files are "kept" (read installed), versions and naming conventions for files and all the rest, folks advocate for what is essentially chaos on the Linux platform.
How do they do it? By making lots of noise about choice. Where choice has put us to date is: Being behind on the desktop. We should have a target system configuration and still leave those who want the status quo to pursue their dreams. Folks, we can do better.
Question is: Why the double standard?
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.
you can imagine [...] if Internet Explorer puts [HTML5] already in there, why do we have Silverlight?
Sadly I think this question will remain rhetorical for the foreseeable future.
Here are some articles on the topic of what is wrong with javascript.
Certainly the speed issue is or has been resolved with impressive recent results. Hopefully that trend will continue.
I don't agree with the strong typing but then that's just me.
Here they are, all with the title "What is wrong with Javascript" funny enough!
http://ayende.com/Blog/archive/2006/02/27/WhatIsWrongWithJavaScript.aspx
http://service.compuskills.co.uk/blog/2007/01/17/what-is-wrong-with-javascript/
http://www.infoworld.com/d/developer-world/getting-smart-about-languages-and-libraries-836
The bottom line for me is that I want MY TOOLS and LANGUAGE(s) that I use for projects rather than having so called "standards" forced on me.
If you like JavaScript all the more power to you.
If you like freedom to choose your own destiny then all the more power to both of us!
Native Clients for POWER USERS in the BROWSER!
http://code.google.com/events/io/sessions/NativeClientUsingNativeCode.html
I'd also prefer SELF in the browser and with Native Client you'll be able to add SELF to your web pages!!!
Yes, javascript sucks for me. Notice I didn't mention the language that I prefer as I didn't really want to get into a language war. I don't care if someone else prefers another language as I pretty much get their reasons as I've been around a while. If someone wants to use some language, SomeLanguage(tm), then please let them!
Native Client now!
How many organizations are still use IE6? Too many.
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!
if you make it good, and we like it, you'd be surprised how fast proprietary technology gets replaced. look at PHP. many of you who work corporate may not be aware, but PHP dominates the majority of sites that belong to individuals and small businesses now. check elance, rentacoder, etc - you'll find that the demand for php projects at least quadruples anything closest.
how did it happen ?
people liked it. it was adequate (then), it was free, it allows you to do anything (now). period. it took off.
before any of you language nazis come up and start trolling about how you dont like php syntax, how there are more 'elite' languages out there, and how php is 'not a language' etc, i should say - i dont give a flying fuck. neither do millions of people who utilize it and who develop on it. so keep it.
Read radical news here
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.
I think I understand your intent conceptually, but would like more clarification. Are you referring to "penises" or "penis' ", as in collectively owned?
In other words, are we talking about a collection of individual penises all grouped together, then referring to them? Or as a metaphorical single penis that is owned by the slashdot bastards as a single unit?
My concern is that it would certainly be easier on the bees if it was a collection of physical penises, rather than an imaginary metaphorical one. The latter would just be cruel to the bees.
From your posts I'm guessing your "other language" is Visual Basic.
And draw with <canvas>.
Flash Player comes with the equivalent of a library for tweening Bezier curves over time. And the Flash editor (3 figures USD) comes with an editor for objects made of Bezier curves. The HTML 5 draft's canvas element currently has neither, to the best of my knowledge.
We're currently in the process of taking our large open source web-based application and re-writing the entire front-end in Flex.
We just got tired of the cross-browser headaches, especially with javascript/layout. As more and more browsers get released into the wild we found ourselves spending a large percentage of time just testing and working around issues with each browser rather then making real progress with the application itself.
Moving to Flex essentially eliminates any cross-browser issues for us, not to mention all the additional goodies it offers.
Browsers haven't implemented the standards that have been out for the last 10 years properly, I'm not holding my breath waiting for them to get it right anytime in the future.
I'd also prefer SELF in the browser and with Native Client you'll be able to add SELF to your web pages!!!
From the front page of the Native Client site, with my emphasis:
That doesn't bode well for compatibility with ARM subnotebooks, ARM PDAs and PDA phones, PowerPC set-top boxes, etc.
And even on devices with a GenuineIntel or AuthenticAMD CPU, it's far from ready. From the release notes:
Why is it that every time a new technology is created we have to phrase it as "taking aim" or "taking on" or being a "[blank] killer?" Why can't we all just get along?
But seriously, why can't we look at this in terms of the development doors that will be opened, and not mind the fact that RIA content will someday probably fall by the wayside? Progress happens, and those companies/individuals/organizations that fail to adapt fall behind and eventually wither. I think we can all agree that HTML5 has the potential to be awesome, let's approach it in terms of how to make it as awesome as it can be, instead of wringing our hands over the fates of the poor, defenseless multinational corporations.
Porquoi?
The bottom line for me is that I want MY TOOLS and LANGUAGE(s) that I use for projects rather than having so called "standards" forced on me.
And yet you appear to be trying to force i686 as a so-called "standard" on me. I don't see how devices with CPUs other than x86 architecture are going to run Native Client programs efficiently.
everything looks like ... you know the rest.
Ok, you've been around for a while. I'm going to infer, from that statement, that you have experience in numerous languages? And, from previous statements, that you don't like parenthesis "goo", so that means C, C++, Objective C, Java, Lisp (man, you must hate lisp...) or any derivatives of the above? What does that leave us with? I guess Python is parenthesis-less, and Perl has less parenthesis. I guess you can do Ruby with relatively few, but you'll still need them.
Seriously, which specific language were you thinking of for programming XML/SGML and the DOM?
Entomologically speaking, the spider is not a bug, it's a feature.
True freedom of choice
I choose an ARM chip for my battery-powered device. How well does Native Client work with it?
Right now you pretty much have to be Flash-literate to make singing/dancing ads that can annoy effectively across the browser genpop, and not many people are. FlashBlock puts today's little pests peacefully to sleep. What will I do when the enemy is indistinguishable from the page code, and anybody can hatch one with two lines of JavaScript?
Not at all. I recently started trying out the language and I've never came across a language I had so much trouble with (assembly and C aside) picking up. And I really like strong typing. Here's hoping we'll have other options than Javascript.
I could easily whip up a dozen articles on how many-a-programmer has fallen in love with JavaScript. In fact, I could give you articles of that nature for any language. Ditto for articles about how language X sucks. Whatever language/tools you like, I'll find you people who hate them.
I agree that it would be *nice* to be able to program using any language you wanted, but it's not the case at the moment (nor for the foreseeable future). I switched from C++ (primarily) to JavaScript/Python, originally not because I *wanted* to, but because I *had* to. I now see the good parts in both, but I can't force my opinions upon you. The point is: If you can't adapt, you're going to have a big problem finding work soon, at least if you want to program *inside* the browser.
(I'd mention that you can use Java/GWT, but from an earlier comment, I take it that won't solve the problem)
Entomologically speaking, the spider is not a bug, it's a feature.
Agreed. What's really needed is a version of Flash (or some third-party tool) that outputs javascripted SVG + HTML5 video.
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.
But isn't this simply another way of saying that it's the guy paying the bills who gets to make the big decisions?
Flash is everywhere and the tools are mature.
Silverlight in Beta has about a forty per-cent share. To the user, having to download these plug-ins doesn't even register as a speed bump.
Whether it makes sense to shoehorn everything into a "standard" browser design strikes me as a question worth asking.
The geek may call them "walled gardens." I tend to think of them as islands.
Distinct communities.
Facebook, MySpace, YouTube, The Sims and so on.
I have a strong suspicion that as these communities evolve they are going to want - and they are going to choose - the tools that work best for them -
whether the geek likes it or not.
There is an Open Source product named Openlaszlo. It is a RIA development platform that can output both Flash 10 and DHTML 4 applications from the same source that are to all intents and purposes identical in function and look. Check them out at http://www.openlaszlo.org/
One factor I'd think would contribute greatly to the success of one over the others is how well a search provider like Google can reasonably analyze and index the content.
Er, regarding your three examples of why you hate javascript:
The first was someone who hasn't properly learned Javascript - the "name" convention for the input box is very beginner stuff. I don't program javascript, I don't program much of anything really, and I know about that one. They have reference books for that sort of thing, and the guy just needs more experience with it. That he avoids it instead of tackling the problems isn't helping his situation with javascript. It would be almost like complaining that you have to separate items in an array with commas in C. If you can't remember that, it's not the language that has a problem.
The second basically said javascript would be great (with a caveat or two) if it weren't associated with useless web crap and turned off all the time.
The third was talking about ALL programming languages, javascript and python were just used as examples.
Quit whining, seriously. It's like complaining that python isn't as fast as C, or that C is harder to write than python. They have their purposes, if you want to do client side browser scripting you should learn javascript.
Besides, as the poster above me noted, you've got quite a bit of selfish double-speak going on.
Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
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.
the tool doesn't exist
Which is exactly my point. Flash is here, and Flash is now. I don't see the free software community coming up with robust HTML 5 authoring tools that replace Flash any time soon.
I wonder what it says about JavaFX that Jonathan Schwartz's blog uses Flash for its video?
http://projectleader.wordpress.com
Do they drink their milkshake?
You know what they say about opinions. They're all fabulous!
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.
something in the future that may work better is not worth considering.
I didn't say it wasn't worth considering. In fact, let me consider it in the same manner in which for-profit businesses will likely consider it: The majority (over 51 percent) of our viewers use Windows Internet Explorer (IE). Because even version 8 of IE doesn't do HTML 5 canvas at all, Flash Player is still more widely deployed than HTML 5 canvas. And even if we could get our viewers to switch to a different web browser, buying n seats of Flash CS from Adobe is cheaper than paying programmers to develop a custom vector animation editor and playback libraries, retraining our artists (many of whom learned Flash in college) on our tool, and paying our artists to redraw all their animations.
Another angle: There's a word for "something in the future that may work better", and that is "vaporware". Duke Nukem Forever was canceled. How likely is it that HTML 5 infrastructure will get to the point where a site with HTML 5-animated comedic short films can compete with Newgrounds, which uses Flash Player, within three years?
How short-sighted.
You're absolutely right: the market is short-sighted.
I guess innovation is dead, cause, you know, we have things. N'stuff.
HTML 5 replacing Flash is like Linux replacing Windows on the home and home office desktop. Windows works well enough, and people know Windows. Flash works well enough, and people know Flash. So a mass switch isn't likely to happen anytime soon.
If all you have is a stud....then everything looks life a heifer?
I guess that's how adobe / ms view HTML 5 anyway.
My pics.
That is one thing MS Silverlight team doesn't understand too.
If you want designers/video guys embrace a new technology, you have to plug into Adobe's tools and Apple Quicktime framework in a perfect, seamless way.
Both Adobe tools and Apple quicktime has no problems with stuff plugging into them and in case of Quicktime, it is actually designed for "components adding new functionality". There is no "evil" to whine about, just an ignorant company who aims to give hell to people who dares not to use their operating system. Well guess what? Designers really use Adobe, Apple technologies and Quicktime (on windows too) so there is no point sending them to Eclipse IDE download. Yes, they suggest them to use Eclipse... Designers... Eclipse... :)
I found this website which demo's the canvas tag in HTML 5. It's basically a small maze, with different textures on the walls.
You're able to change the texture settings to either Lower, Low, Medium, or High.
Working my way up with the settings, using the latest Firefox 3.5 beta, Opera 10 Beta, and Google Chrome (just a straight download, no beta if there is one).. and on my machine I found:
It's not quite the results I was expecting. Granted it's just one test on a very, very premature standard, but being the other two are beta releases showing off and fixing up the newest and greatest, I figured Opera would take the lead with Chrome and Firefox near each other. I didn't try Safari, but if anyone else has all the HTML 5 compatible browsers installed give it a shot and see what you get.
If anyone else knows any other HTML 5 semi-intense webpages that exist yet, or some way to compare how the browsers stack up with HTML 5 so far, please post as I'd be interested in checking it out
That huge framework install with all the functionality still hurts quicktime, in case of Windows Media, you have already got it forcibly installed and it also uses undocumented goods of Windows to perform better. Linux? No official support. Real? Well, people still think it is spyware even while it is open source.
All these tools are in fact superior to Flash for embedding video, especially Real Player is really in 11th generation. Why they fail? Because they don't have Adobe design tools for use of real artists (designers) and they are still STUPID (hear me Apple) to add additional stuff to that already bulky download.
I always feel sad for using Flash to embed videos with the functionality missing from it but as I can't tell people to "download 30 mb application" or "give up your IE and use that open source browser" (sorry!), I embed Flash.
That was my point. Quicktime is a great technology being wasted by couple of idiots at Apple Inc. You know, the idiots insisted on asking $$$ for full screen playback for years. They couldn't seperate the "player" and "recorder"... They owned 80% of video market share back in worst days of Apple, can you believe?
Comment removed based on user account deletion
There have been 400M downloads of Silverlight so far.
That's more than the total market share of Firefox + Safari + Chrome (+ Linux + Mac + iPhone + Android if you're thinking platforms). So Silverlight's already a bigger audience than every browser NOT IE running on Windows.
Popfly is hardly meant to be the big Silverlight install driver :). In the USA, the highest profile Silverlight projects have probably been Netflix and the Olympics (Beijing and soon Vancouver), with the Masters and NCAA March Madness as recent big ones.
Because so much of media is geoblocked, the big Silverlight drivers vary by market. Russia has RuTube, South Korea has all major broadcasters and the leading search provider. France just had their big Tennis tournament.
My video compression blog
Google is a Canvas/HTML5 backer, both via their various web properties and via Chrome.
And YouTube is already experimenting with HTML5 instead of flash (http://www.youtube.com/html5)
All it will take is a web property like YouTube to put a nice big link up there saying "hey, look at how much cooler YouTube could be without IE), and people will start dropping it like mad.
Let's see how many times we can say "RIA" in the summary and top rated comments without saying what the acronym is!
What Google could do is to see what browser is being used and they will offer the 'best' user experience for the end user. Go to Browserspy.dk and look at all of the Info at their disposal. The can offer HTML5 if your browser supports that. They could offer JavaFX is you have Java 6 installed and enabled. They can then use Silverlight or Flash if needed. If I am running Safari, and you are running Chrome, we will have a better experience than my friend with IE. She will not have a 'degraded' QoS as much as we will have an enhanced experience.
Think global, act loco
You are partly right in what you are saying, but wrong if you are implying that Silverlight is anything less than a big leap forward over Flash and Javascript. As a developer, the first time I used Silverlight I swore I'd never go back to AJAX or anything else. It is so easy, well designed, well integrated with Visual Studio and uses the same .Net languages I'm used to. It really feels elegant to use in many ways, and it's much faster to make something in Silverlight than other technologies, ESPECIALLY AJAX.
However, after the initial euphoria wore off, I ended up choosing not to do anything in Silverlight and to design my new projects using AJAX, again. The main reason was that, because Silverlight is not heavily adopted yet, I don't know what support will be like five years from now. Will it be dropped by Microsoft due to lack of adoption? Also, can I count on developers moving into my role behind me to know Silverlight, since it isn't heavily used right now? I think it is an outstanding technology, but until it's more widely adopted, its status will be uncertain. And that's the real catch-22... as long as it is uncertain, more people won't adopt it, at least not quickly. And that, I think, is the biggest reason it is failing to take any market share from Flash. Everyone is waiting around to see if it goes anywhere, and as long as everyone just waits, Silverlight can't take off despite being a good technology.
And this brings up an interesting side question: Most likely if there was a major, open industry standard around Silverlight that anyone could use, the uncertainty would be dissolved and adoption would start. Does this situation indicate that the market is no longer receptive to proprietary standards (at least in areas such as the web, where open standards are the norm)?
Beware of bugs in the above code; I have only proved it correct, not tried it.
I love the fact that despite the mighty MSFT with its VBScript/JScript/.NET, Sun's Java and JavaFX, and Adobe's Flash and ActionScript in combined assult on common, non-plug-in, web standards, JavaScript simply refuses to die and is more popular than ever. Despite the lack of dedicated tools support from major vendors. It shows the majority of web users simply just want a free web browser that works without fuss. How often do you actually hear the majority commenters rave about a total Flash website? How about the other way around? The popularity of Flash has only 2 main reasons - 1) Stream videos (mainly porn) in a way the users cannot download; 2) flashy banner ads only the designers and advertisers themselves love. The vendor tools that supposedly make it *EASY* to develop only make it easy to develop crap. The danger of vendor plug-in is this - if you can view the web and vendor specific content with just the vendor plug-in, why do you need the web browser? Don't let them cripple the web browser or hinder its evolution.
"Does this situation indicate that the market is no longer receptive to proprietary standards (at least in areas such as the web, where open standards are the norm)?" I definitly think so and a lot of other webdevelopers certainly think so too.
New things are always on the horizon
First of all, the rule is, if Microsoft doesn't support HTML 5 in Internet Explorer, then we won't see it being used. Also, we won't see companies like Adobe investing heavily in supporting HTML 5 in development tools since it competes with their Flash business and with their server business. Microsoft won't make much effort to support HTML 5 since they never considered it interesting to begin with. After all, they squashed EcmaScript 4 since as far as they were concerned, you don't need it when you have better systems like .NET and Flash.
On the other hand, like most other HTML elements out there, portions of HTML5 will be adopted as people see them being convenient to use as opposed to alternatives. But, what Ian Hickson (know him personally, nice guy, but has always lacked any realistic grip. Always assumes that people will gladly inconvenience themselves so long as there's an "open" standard as opposed to one like Flash), doesn't realize is, is that for a new tag to make it into HTML and propagate to all major browsers can take years. For a cool new feature to make it into Flash and propagate to nearly every computer that views a page that makes use of that feature is as fast as the download of the feature.
Plug-ins themselves aren't the problem. Flash is not the only solution out there thanks to Silverlight, so there are no alternatives. In fact, plug-ins are easy to write (I know since I implemented plug-in support in one of the major browsers) and because of what can be learned from Macromedia/Adobe, they are now quite easy to deploy. Using a tool like Trolltech Qt combined with OpenGL makes it even easier since you can write the plug-in once and deploy it to pretty much every browser with little more than makefile changes. As a matter of fact, I've been very tempted to make a sample which simply wraps the Qt SVG support to do the same in order to make SVG a plug-in with consistent behavior across all browsers instead of the fiasco it is now.
The fact is, plug-ins like Flash and Silverlight are possibly the best thing about the web since it is possible to extend the browser from a single central source as opposed to waiting 5-10 years for a W3C spec to be made and propagate. Also, they're even better than a W3C spec since they can provide consistent results across platforms.
The real important feature of HTML5 is the <video> tag which will only prove itself useful if browsers support it. Firefox, Chrome, Safari and of course Opera are obviously going to support it. But the question is, whether Internet Explorer will. And frankly, I'm sceptical about this.
W3C screwed up the video tag since they didn't make a true investment in multimedia as part of the standard. They didn't want to use H.264 for the obvious reasons, but more importantly, they should have made a formal container specification and streaming packetized protocol specification for use with it. Now, simply supporting the <video> tag isn't good enough. Now all the browsers have to standardize on what formats are baseline, and frankly, I'm waiting for sleeper patents to start popping up everywhere once all the major browsers support Ogg.
Comparing HTML5 with JavaFX or Silverlight is like comparing apples with oranges.
JavaFX and Silverlight use compiled programming languages with everything you can expect from a modern programming language like threads, and annotations. Furthermore they have the complete toolset to create, refactor, debug and test programs offline.
HTML5/CSS doesnt even have a decent programming language. There is only java script, which is a interpreted, week-typed script language which is very slow and doesn't support essential features like threads for example.
I think HTML5 will make Flash obsolete, but Silverlight and JavaFX play in a different leage.
For several reasons:
1. Microsoft doesn't give a shit about it. Therefore enterprise users won't give a shit.
2. Even if Microsoft does give a shit, neither Apple nor Microsoft will support Ogg Theora. Therefore Linux is SOL again.
3. Apply #1 and 2 to audio standards as well. No common, open, royalty free, pre-installed standard across all platforms == epic fail.
The main power of Flash right now is that once you install the plugin, you might as well forget all that BS about paying for codecs on all three major platforms. It's all in there. It's convenient. It's sufficient.
Mod down!
Amazingly enough, firefox doesn't actually do everything.
PBBG's will fix the problem.
When we begin to design advanced UI's which required HTML5 people begin to change their browsers.
[My english is better than most other people's Turkish, so please point out mistakes politely. Thank you.]
I've been using Flex more and more where possible, simply because it lets me focus on what I care about, the value that my code brings to things, NOT trying to make sure it works in X different browsers that each need to be tweaked, etc.
When using Adobe (or MS for the color of a flash, Silverlight), I have one vendor, with one vision, one set of design tools, one set of help files, where most of the examples I find on the web I can use immediately and get back to work.
With HTML5, I have:
HTML Committee (w3c, etc.)
Javascript committee
CSS Committee
1 of many javascript libraries, like Prototype, JQuery, etc.
Then you have:
Microsoft (IE)
Mozilla (FF)
Safari
Google
Opera, etc.
each with their own implementations of the 3 committees work, that are partial and flaky and require the above mentioned javascript frameworks to even begin to be useful since they incorporate some of those browser work arounds. But then everytime you look for an example on the web, you find something that uses the framework you aren't using, so you have to keep looking or rewrite code you really have no interest in as part of your business.
Until there is a unified framework that is actually Write Once, Run and look the same Anywhere as Flex (or Silverlight), there will be a place for them. MXML (and possibly XAML) are simply a huge relief to work with after dealing with the morass of HTML/JS/CSS dev.
I absolutely agree that the mobile market is a BIG issue that needs to be dealt with, with Flex-Flash/Silverlight though.
http://blog.slaingod.com
If Microsoft choose to not implement HTML5 + CSS3 for 10 years, then HTML5 + CSS3 is, to all intents and purposes, 10 years out.
There's no point in using the parts of CSS2 that IE6/7 doesn't support on your web page, because the number of people using those browsers is so big and un-ignorable that you have to find a way to do what you want using the bits that it does support. But once you've done that, what you've done generally looks correct in modern browsers too. Using the bits of CSS that IE doesn't support is therefore mostly redundant and will add to your maintenance headaches. Hence, as a developer, you're generally stuck with whatever IE chooses to support.
Why doesn't the gene pool have a life guard?
And even on devices with a GenuineIntel or AuthenticAMD CPU, it's far from ready. From the release notes:
Unfortunately, this is a more fundamental problem. Native Client makes use of x86 CPU's segmentation features to provide memory protection. These are not available on 64-bit CPUs (except when running a program in 32-bit mode). So native client will NEVER work for a fully 64-bit browser. I do not see any way of providing equivalent memory protection without segmentation, short of dynamic instruction rewriting (emulator-style) which has an order of magnitude more overhead (say, 2x overhead, versus 5% overhead for native client).
> That allows you to program in java
GWT ist a transpiler which translates Java SYNTAX to JavaScript syntax. It comes with a set of proprietary Java classes which wrap JavaScript equivalents.
Instead of learning JavaScript, which you have to learn anyway as soon as you want to use GWT's "native javascript interface', you must learn Java and understand the non-standard classes that GWT provides.
It doesn't buy you anything but a complex additional layer. It might sound appealing at first, but as soon as you start using it, you will soon find yourself writing plain JavaScript code anyway.
I read the headline too fast and my brain saw:
"HTML takes aim at Fleshlight"
The web has come of age!
Is the key phrase. Given that one of the RIA tool vendors also controls and significant percentage of browser adoption of HTML 5/CSS 3 features I can only see a viable future for Flash in the medium term.
There's little you can do in Flash/Flex that you can't do in (D)HTML/Javascript/Ajax. I say this as a Flex developer. The key thing is though that Flex provides a single consistent environment to develop on whilst developing for HTML is a nightmarish, byzantine, tangled knot of subtle incompatibilities and shifting target environments.
Puzzle Daze is now my job
I hate to break it to you, but 99% of the time, when your HS guidance counseler says you won't be President, they are usually right. Once you admit you are a troll that ruined your life, well, it all becomes easier to deal with and potentially correct.
FYI: freej 1.0 will be released in July, it is a vision mixer engine (2d) with a javascript interpreter (xulrunner) and python bindings http://freej.dyne.org/
Open standards please, please, please, one standard for all, end of all this bs my proprietary framework is better than yours debate... just roll the best proven features of all these alternatives in!
By pointless crap, he meant eye-candy that is useless, with fricking animations everywhere that distract you from the actual content and that and only gets in the way of productivity and accessibility. I don't ever remember seeing a Flash website that had an usable interface.
google is already creating html5 sites for alot of their products (like gmail, gdocs, gcal en youtube), and their user base is massive. that might be what ms needs to finally implement html5. in ie8 they also got with the program and had pretty good html and css standards support.
the problem you point out for the tag is valid (ogg theora vs h.264) but browsers can also handle more than 1 image format for . i'm also not aware of sleeper patents or other problems with the use of the proprietary jpeg format
Flash, JFX and Silverlight are a bloated crap software. Though, it is not the biggest issue. The problem is to make web propietary, all of us were in the hands of these corporations.
Let's put them in the recycle bin :-)
The RIA guys are quoted as saying they're not worried, because HTML 5 + CSS 3 is 10 years out.
Does anyone else see a pattern here? Disruptive open standard is proposed. Committee is formulated to advance the standard. Microsoft gets involved. The standard languishes for years. SVG. CalDAV. XML Forms. Etc. Microsoft's strategy is clear: delay and disrupt progress on any and all open standards which pose a threat to their proprietary alternatives. Putting Microsoft on an open standards committee is like putting Rush Limbaugh on Barack Obama's campaign team.
Sure, /if/ your content is the type that can be presented in a text-oriented, page-by-page manner, then creating simple, barebones HTML pages is smart coding.
But every design has its limits. Try pushing at the edges of HTML, and it gets painful, fast. On one project I audited, we were spending 75% of our coding time on browser workarounds. Switching to a RIA was a huge time-saver. At the edges of user interface design, HTML compatibility is thoroughly broken.
However, your instinct that the simplest designs are usually the best is spot-on. This is exactly kind of back-to-the-basics thinking that is behind REST, Atom, JSON, and other web-centric techniques.
"We receive as friendly that which agrees with, we resist with dislike that which opposes us" - Faraday
I wouldn't worry about developers behind you on projects. The next sure thing is very hard to predict. Standards within languages change, ways of accessing data change or thinking about problems. Paradigm shifts happen quickly and as "close to the metal" is getting less popular language flexibility is increasing.
I am a developer in a very similar boat. Recently I picked up with a larger organization that is moving a lot of their technology to the web (and off of thick client on Citrix).
I've been doing web development for years, long before AJAX was AJAX. But the shop here has some guys who have done only minimal web development. In order to spin them up on serious web development we're talking about teaching them HTML, CSS, Javascript, ASP.Net's model, and the AJAX model, coupled with the challenges of developing for multiple platforms.
Well, I had been playing around with Silverlight 1 and Beta 2 for a while, and I was having the same feelings as you. It's so much more elegant, so much more simple, so much faster to develop with.
I also have fears about support. Especially with SL 2 as most outstanding bugs have been fixed in SL 3 (due out in Q4) so a lot of the support is just "Install SL 3 Beta", which doesn't really fly in a corporate environment.
But I'm pushing ahead in this direction anyway. For a internal development where I can kick out better looking apps in less time with a higher level of usability, it just makes sense. For external development, I'm still in the air though, I'd like to see more adoption and SL 3 stable before pushing for public projects.
I am still excited for HTML 5, but I'm not expecting it to be a viable development platform for at least another 3-5 years. And with the rate of adoption in most corporations, I'd venture that the 5+ year time frame is more likely.
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
... welcome our standards-compliant overlords (and it's about damn time)
You must wait a little bit before using this resource; please try again later.
The structure of packages, the strong typing of variables, classes and functions, and many of the classes ARE similar to java
'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.
What? I have to imagine the Silverlight team? Don't they exist?
Note to editors: I think the point of liberally sprinkling square-bracketed words around your quotes is to ensure the sentences make sense.
By pointless crap, he meant eye-candy that is useless, with fricking animations everywhere that distract you from the actual content and that and only gets in the way of productivity and accessibility. I don't ever remember seeing a Flash website that had an usable interface.
Pointless animations that distract from the content are bad graphic/web design - the work of the talentless hacks JobyOne was probably talking about.
HTML needn't be the end for innovative web software, but it surely could be a long overdue end to those damned plug-ins! The reason those plug-in required software products deserve to die a terrible death is that those programs have hampered commerce and made most customers' web experience, miserable!. If you were running a traditional store, you would not stop customers at the door and insist that they don a monkey suit in order to shop. This is somewhat like what those plug-in software companies did. What macromedia and their ilk were saying was, "Either wear the monkey suit, or take your business somewhere else." recent research has shown that eighty-eight percent of web users refuse to pause to download plug-ins; they simply take their business elsewhere. The fact that most of the world is still using low-bandwidth connections (estimated at eighty percent of users) adds to the problems created by demands for downloading plug-ins before gaining access to commercial sites. With HTML5, business should experience a significant increase in online traffic and sales. If HTML5 lives up to expectations, this one change could be the key factor in some business segments starting on the road to economic recovery. Let's hope the HTML5 implementation happens quickly.
re: "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"
The new video backend and distribution system (as well as the new client) were used throughout Spring Training. The biggest problem this spring was the installation of the separate NexDef stream manager, which was also a difficulty during previous seasons... overall the forums were much, much happier this year:
http://www.mlbsupport.com/forum/viewforum.php?f=3
Thanks for the link to the Huffington Post piece. It describes the Gameday Audio system, which is not the Flash video client or interactive display.
(For what it's worth, I had been impressed with the support staff at the MLB.com forums.)
jd/adobe
JavaScript is terrible. jQuery fixes it.