HTML 5 Canvas Experiment Hints At Things To Come
An anonymous reader writes with an interesting and impressive demonstration of modern browsers' HTML 5 capabilities. "From the 9elements blog: 'HTML5 is getting a lot of love lately. With the arrival of Firefox 3.5, Safari 4 and the new 3.0 beta of Google Chrome, browsers support some great new features including canvas and the new audio/video tags. [...] We've created a little experiment which loads 100 tweets related to HTML 5 and displays them using a javascript-based particle engine.' The site warns "(beware: sophisticated browser needed)"; Firefox 3.5 seems to work fine.
How about some actual cool examples like this instead?
I don't need to test my programs.. I have an error correcting modem.
KDE4's Konqueror handled the page for me much better than did Firefox. I have Firefox 3.5.1 and Konqueror 4.2.98. While Konqueror gave me no sound and Firefox did, when I tried it with Firefox, it ate up so many resources that I couldn't even get my key combo for xkill to work. Fortunately, I was able to get to a virtual terminal and kill it, but it wound up crashing my window manager. Konqueror did much better. I need to try it with Opera (which I understand is supposed to be very good).
Anyway, it's pretty neat. I think I'll start making some pages for the heck of it and put it on my local network.
Omnes tuae crepidines sunt nobis sunt. Ascendo tuum!
I was sort of thinking the same things.
Now I'm wondering if the things I hate about Flash wasn't the actual software but what people were doing with it.
Is eliminating Flash not enough? HTML5 is open and (being) standardised; anyone is free to implement it. (And you can see there are already several competing implementations in progress) Flash is a proprietary platform and you are solely dependant on the whims of Adobe. If even just for the lack of choice, Flash is a worse platform. Nothing's forcing Adobe to fix their player, while the HTML5 browsers definitely have some competition going on and are improving at an amazing rate - and in fact when HTML5 starts to pick up, Adobe will be forced to do something, as HTML5 itself will be competition to Flash.
Some people complain about how fast that thing runs (or how much CPU usage it takes), but I bet a flash version would not be even twice as fast, and Flash has existed for how long compared to browser support for HTML5 technologies?
That's why I think it's awesome that HTML5 includes sound. You can't block the sound from a plugin that's executable code that does whatever it wants, however browser makers (and extension writers) can put settings options to let you opt-out for the sounds. Or prevent things from playing until you switch to the tab that wants to play them.
Slashdot anagrams to "Sad Sloth"