Slashdot Mirror

← Back to Stories (view on slashdot.org)

How HTML5 Will Change the Web

Posted by CmdrTaco on from the heard-this-before dept.

snydeq writes "InfoWorld's Peter Wayner looks beyond the codec and plug-in wars to examine nine areas where HTML5 will have a significant impact on Web development. From enabling more interactive graphics, to tapping local file storage, to geolocation, HTML5 is rife with rich capabilities — and may even improve our ability to secure applications delivered via the Web, Wayner writes. But the most important impact of HTML5 will be its ability to simplify Web development itself: 'HTML5 offers one language (JavaScript), one data model (XML and DOM), and one set of layout rules (CSS) to bind text, audio, video, and graphics. The challenge of making something beautiful is still immense, but it's simpler to work with a unified standard.'"

5 of 208 comments (clear)

  1. I love flashblock by anss123 · · Score: 4, Interesting

    Will there be possible to have "CanvasBlock" on future browsers or are we stuck with CPU eating html5 animations?

  2. Re:"Offers one way of doing things" by Lumbre · · Score: 3, Interesting

    Frankly, I doubt that the popular browsers will even have a reliable implementation of the standard until at least 2013

    I doubt IE will ever have a reliable implementation for anything. HTML5 surely aims to simplify web development, but MS aims to use their proprietary BS, tags, and implementations. Just look at their box model. Look at all the extra time we have to take to develop for IE users.

    Plus, there are accessibility issues we have to overcome. We also need to develop for that small fraction of the population who use text browsers, those who are blind and have text read to them, those who don't install Flash (for good reason), those that disable JavaScript, etc.

  3. CHANGE IS ALREADY HERE by Digana · · Score: 4, Interesting

    ZOMBO

  4. The one real data model: XML by improfane · · Score: 5, Interesting

    Why are we using HTML5 and not XHTML 2?

    XML abuses aside, XHTML is superior to HTML5.

    HTML5 requires a more complex parser than XHTML ever will. XHTML can be validated for correctness, HTML5 is more difficult to do so.

    I honestly don't understand the reason for following the HTML route. XHTML is already in an industry understood format that tools already exist for.

    The market rarely reflects a superior technology. I still support XHTML. HTML5 is messy, ugly and a kludge.

    All that needs to happen is to transfer some of the newer tags of HTML5 into XHTML. Perhaps we can borrow from the microformat peeps? Afterall, it's supposed to be modular.

    --
    Slashdot needs Geekcode | Can anyone recommend any good SCIFI? My tastes: Foundation, Startide Rising, CITY, Ringworld,
    1. Re:The one real data model: XML by mortonda · · Score: 3, Interesting

      Why are we using HTML5 and not XHTML 2?

      XML abuses aside, XHTML is superior to HTML5.

      Go read http://diveintohtml5.org/

      Essentially, the argument is, make it easy for the users - the web programmers, not the browser programmers, and to allow the browsers to incrementally implement the standard, rather than an all or nothing that no one will do. . Telling the browser to error out when the html is not correct or supported is user UNfriendly. HTML5 provides a graceful way to handle it.