| > Flash needs to be killed.
| > It hogs the CPU, poses security risks
|
| Why would HTML5 video not hog the CPU
I think he's talking about hogging the limited
power and battery life of tablets. But you make
a relevant point in general. I recently updated
Pale Moon, a "lightweight" version of Firefox. It's
using 60 MB of RAM just to sit there.
Extreme use of javascript in HTML for interactive
pages and online services has made webpage
rendering far more demanding than it used to be.
That's the "big new" change, more so than HTML 5.
HTML 5 is mainly the addition of tags to HTML for
multimedia and changes to adapt to highly interactive
pages:
http://dev.w3.org/html5/spec/single-page.html
If you view the source code of a webpage and see
this at the top: <!DOCTYPE html> then it's HTML 5.
It won't look so different from HTML 4.
There have been HTML methods to embed sound
and video in the past. HTML5 just tries to integrate
the whole thing better, with player plugins built into
the browser.
The big change, whether pre-HTML5 or post-HTML5
has been heavy use of javascript for extreme
interactiveness, with the ability to spy, track, display
targetted ads dynamically, respond smoothly to user
input without having to reload the page, etc. Commercial
online services are stretching script to its limits, while
browser makers continue to improve script parsing, in
an attempt to make pages highly interactive. Many pages
that used to be 40-60 KB might now be 200-300 KB.
Jquery, a popular javascript library, is about 100 KB by
itself. That is, the script has been getting so complex
that people are using pre-written scripts of 100 KB, outside
of the actual webpage, and then calling functions in those
external scripts. When you go to Google it looks like a
very simple webpage, but it's become closer to software.
The HTML is minimal compared to the amount of script
they're using.
| ...and not pose security risks?
|
HTML 5 does pose security risks. But it's not really
the HTML part that we're talking about. Flash, Acrobat Reader
and Java have all been common security risks. In HTML 5,
browser plugins provide video play. And as nospam pointed
out, even Adobe is working on trying to package script and
CSS functionality to mimic Flash cartoons, in case support
for Flash sours. All of that is high risk. It all boils down to
the same thing. Script is the main risk. Interactiveness is risky,
because it requires some kind of executable software.
Interactiveness almost always requires script. Flash just
provides additional "attack vectors".
No one wants to face those facts. Commercial websites
want to provide a highly functional software interface. They
want interactive-TV services that you'll pay for. Likewise,
people want to shop, set preferences, Facebook, watch
video in a webpage, etc. Security and privacy can *never*
be adequate in that scenario.
The original purpose of script was to do simple, dynamic
things like making a button glow when the mouse is over it.
(Much of that functionality is now possible with CSS.)
Webpages were originally designed for static display. HTML
has been stretched far beyond the original intention by
stretching javascript to do things *it* was never intended
to do.
Java, Flash (and ActiveX controls...Flash is ActiveX in IE)
were early attempts to embed software in webpages. People
are still trying to do that in one way or another. Not to defend
Flash, but it's been a problem for years and much of its use
is for annoying animations that no one wants to see in the
firs place. No one would be singling it out now if Steve Jobs
hadn't publicly added the issue to his official religious doctrine.