Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Software The Internet Technology

HTML5: It's Already Everywhere, Even In Mobile 133

electronic convict writes: Tom Dale has never been shy, and in a Q&A with Matt Asay on ReadWrite, the EmberJS co-founder and JavaScript evangelist makes the outspoken claim that open Web technologies are already everywhere, even in native mobile apps, and that it's only a matter of time before they catch up to "all the capabilities of a native, proprietary platform." Take that, Web-is-dead doomsayers.

Dale has plenty more to say, calling Google an "adolescent behemoth" that's belatedly embracing open-Web technologies in mobile, lauding Apple's Nitro JS engine and belittling the idea that Web apps have to look and feel the same as native apps for the open Web to triumph. His bottom line: "[I]t's not hard to see that the future of the Web on mobile is a happy one."
This discussion has been archived. No new comments can be posted.

HTML5: It's Already Everywhere, Even In Mobile

Comments Filter:
  • by MouseTheLuckyDog ( 2752443 ) on Tuesday November 18, 2014 @12:27AM (#48408617)

    My understanding is that it is still just HTML, but the way some people describe it, it sounds like the second coming of C.

    • Sorry that should be HTML5 in the title not HTML.

      • by ShieldW0lf ( 601553 ) on Tuesday November 18, 2014 @12:44AM (#48408677) Journal

        It's less secure than its predecessors, allowing you to do more with it than you could before.

        That sounds like a troll, but it's not. A lot of what's billed as innovation in this sphere was thought of by many people before, but the platform was intentionally designed to make it impossible for security reasons.

        • It wasn't that a lot of these things couldn't be done before, it was that non-realtime media, non-interactive media, and scripted pseudo-interactive media (cgi scripts) should not all be lumped together.

          But now all that has been thrown aside and every day one has to wonder just what trick you have no way of auditing is going to pop up in your browser today, be it mundane or nefarious.

          • by Anonymous Coward on Tuesday November 18, 2014 @02:16AM (#48408877)

            It wasn't that a lot of these things couldn't be done before, it was that non-realtime media, non-interactive media, and scripted pseudo-interactive media (cgi scripts) should not all be lumped together.

            For example, the article on readwriteweb does nothing if Javashit is disabled, yet it's just a static piece of text with some images and could have been just as effectively rendered in HTML 3.0 like any other motherfuckingwebsite.com [motherfuckingwebsite.com].

            Sad thing is, HTML 3.0 is more responsive than most of the shit I see today. HTML 3.0 used to just wrap words at the end of the screen or the window, no matter what the "designer" wanted. Now, when the "designer" wants a 6-inch minimum width, the text is unreadable on mobile unless you're willing to scroll back and forth for EVERY FUCKING LINE OF TEXT. And when the "designer" wants a 500-pixel maximum width,
            the website
            looks like this
            on the
            desktop.

            Fuck web design. Fuck web designers. And increasingly, fuck the web.

            • by Ksevio ( 865461 )
              Sure that may be the case with what HTML 3.0 was designed for, but remember how people actually used it?

              Designers wanted their minimum width columns so there were tables inside tables everywhere!
            • And when the "designer" wants a 500-pixel maximum width,
              the website
              looks like this
              on the
              desktop.

              500px for body at a "normal" font size (16px) is 31em. Studies show that column widths wider than about 40em (80 columns) make text harder for most people to read because they end up skipping or repeating lines.

              • by Anonymous Coward

                500px for body at a "normal" font size (16px) is 31em. Studies show that column widths wider than about 40em (80 columns) make text harder for most people to read because they end up skipping or repeating lines.

                And you have no idea how many columns of text my web browser is showing. I have a 1920x1200 screen. I'm not so fucking retarded as to maximize my browser window, and that's precisely because I have a 1920x1200 screen. The browser window is usually squarish, and most websites (pre-web2.0 shit) render

                • by tepples ( 727027 )

                  There are too many browsers, too many different screens, and too many physical form factors out there. Just fucking let the browser render the content the way it wants to.

                  So how should a web site provide a good reading experience the majority, who apparently are "so fucking retarded as to maximize [their] browser window" even on a 1920px-wide screen?

                  • So how should a web site provide a good reading experience the majority, who apparently are "so fucking retarded as to maximize [their] browser window" even on a 1920px-wide screen?

                    Gee, if only there were a way to suggest (but not mandate) that the browser render a piece of text in a certain manner. A "style", if you will. The specification of such a "style" might include a maximum width [mozilla.org]. Well, I guess no such thing could ever exist, so in order to format that text the server will need to send a whole pile

                    • by tepples ( 727027 )
                      I'm aware of max-width in CSS. But the AC who wrote this comment [slashdot.org] objects to the use of max-width: 31em. It sounds like the AC objects to referencing a style sheet from an HTML document at all, instead preferring that everything look unstyled like the mid-1990s web, citing motherfuckingwebsite.com which uses the subset of HTML that existed in the mid-1990s.
            • Why do I have the sudden urge to stand on the sidewalk in front of this guy's house with my toe poised half an inch above his grass?
        • by NotInHere ( 3654617 ) on Tuesday November 18, 2014 @01:29AM (#48408791)

          but the platform was intentionally designed to make it impossible for security reasons.

          Perhaps thats true for some technologies, but as user agents didn't add those features to the web, all of those shiny features landed in flash or silverlight and ended up being less secure and more broken than before. Soon every website told you to install flash because it was so new and so cool.

          So browser vendors had the choice: either add the features to the browsers themselfes, or rely on one company (Adobe, silverlight came later) and their "Browser inside a Browser".

          Of course HTML5 is less secure, and especially WebGL allows the web (traditionally a very dangerous place) to access the graphics card without a dense safety net. But otherwise you would have unity web player or other technologies, which are basically punching holes exactly there where you build your safety net.

          HTML5 isn't less secure because people wanted it to be less secure. They wanted to obsolete plugins, but still meet the Web's users demands. Do you have flash installed?

          • Of course HTML5 is less secure, and especially WebGL allows the web (traditionally a very dangerous place) to access the graphics card without a dense safety net

            Doesn't sound exactly true anymore now that chips like Kaveri basically allow you to run graphics code on top of the virtual memory circuitry.

    • by Anonymous Coward

      My understanding is that it is still just HTML, but the way some people describe it, it sounds like the second coming of C.

      It's certainly a lot easier to do cross-platform user interfaces in HTML5 than it is in C.

      • by Anonymous Coward

        My understanding is that it is still just HTML, but the way some people describe it, it sounds like the second coming of C.

        It's certainly a lot easier to do cross-platform user interfaces in HTML5 than it is in C.

        That's true in any language that includes a UI library, simply because C does not include one.

        UI-aside, C is a lot more portable than HTML5 is.

        • by exomondo ( 1725132 ) on Tuesday November 18, 2014 @02:58AM (#48409001)

          UI-aside, C is a lot more portable than HTML5 is.

          Sure if you're writing embedded applications, backend server programs or scientific computing applications HTML5 is probably not the best choice but if you're talking end-user facing programs then it's going to be portable across all the major (and most of the minor) platforms.

          • by Anonymous Coward

            So.. if you are writing for the personal computer something that the user has to see graphically HTML beats C hands down? Utilising a whole software stack that's mostly written in C ,-D

            • So.. if you are writing for the personal computer something that the user has to see graphically HTML beats C hands down?

              Not necessarily.

              Utilising a whole software stack that's mostly written in C ,-D

              Yes, most higher level languages run on platforms written in C, that doesn't mean C is the perfect language for everything.

            • by tepples ( 727027 )
              C and C++ are compiled for a particular instruction set and linked for a particular platform. When a developer has to reach to reach users on a dozen different platforms, some of which have onerous developer qualifications, it's more efficient for a developer to target a compatibility layer implemented in C or in C++.
        • by Tablizer ( 95088 )

          UI-aside, C is a lot more portable than HTML5 is.

          That's like comparing apples to peacocks.
           

    • by LordLucless ( 582312 ) on Tuesday November 18, 2014 @12:50AM (#48408697)

      It's basically just a bunch of new features that are wrapped up into a bundle with the label "version 5" slapped on it. It's usually accompanied by CSS3, which adds new features for styling stuff.

      There are two reasons people like HTML5, in my experience. Firstly, the canvas element lets you do arbitrary drawing with javascript, opening up a large range of applications for pure-HTML that used to rely on stuff like Flash or Applets (most notably games). Secondly, HTML5 does a lot of stuff natively, that used to have to be added (somewhat hackishly) by javascript and UI libraries - form validation, colour pickers, date selectors. When you add CSS3 into the mix, you can make quite rich UIs with very little (if any) use of javascript.

      Basically, HTML5 will let us retire a whole bunch of crufty old legacy hacks from the bad days (Javascript everywhere, Flash, Applets, etc)

      • Well that is all and good but IE does not support any of the new input types, the new minimum browser supported for most people is now IE9, which does have canvas and SVG, but is missing a bunch of stuff like input types and CSS gradients. IE9 is the new IE6 and is here to stay for many years.

        • by Shados ( 741919 )

          Depends what you do though. Making a mass market customer facing e-commerce website? Yeah, IE9's probably your minimum. Maybe even IE8 for some cases.

          Making an internal portal? You probably can go IE11.

          Mac-only shop? You can even drop IE now and just go safari/chrome/firefox.

          Not as lucky, but you have a dashboard for a marketing or HR system? You probably can mandate IE10 and up. Any company who cannot accommodate that will be stuck on SAP and Oracle anyway.

          Making a desktop app with HTML5 stuff? Well, you'r

        • IE9 is the new IE6 and is here to stay for many years.

          "Many" here means just under two and a half. Security updates for Windows Vista end in April 11, 2017, and all versions of desktop Windows newer than Windows Vista support IE 10 or later. And unless you have a substantial audience actually using IE on Windows Vista, you can probably provide a "gracefully degraded" experience for IE 9 and recommend Firefox for the full experience.

      • by asylumx ( 881307 ) on Tuesday November 18, 2014 @08:51AM (#48410127)

        Basically, HTML5 will let us retire a whole bunch of crufty old legacy hacks from the bad days (Javascript everywhere, Flash, Applets, etc)

        You must be new to the world of programming -- old technology never dies! MWA HA HA HA!!!

        • By "retire" I mean "not use anymore". Of course, we'll still be stuck supporting the legacy crap for decades to come. Much as we'll be stuck supporting HTML5 when the new shiny comes over the horizon.

    • HTML5 introduces several useful features which were poorly implemented with shims in HTML. Example: Canvas element now allows for graphics without a plugin. New input types will _lessen_ the need for Javascript datepickers, field type validation. HTML allows for offline application and data so you can launch web applications offline.

      All of this depends on browser support though. Input types are not universally implemented or even clearly specified as to their behavior in specifications. Canvas element glitt

    • by stms ( 1132653 ) on Tuesday November 18, 2014 @12:56AM (#48408717)

      because you can make amazing websites like zombocom [html5zombo.com]

    • Re: (Score:2, Insightful)

      by Anonymous Coward

      No that's basically it.

      Long story short, HTML5 came about around the same time as the rise of hipsters, the type of people who produce crappy little "artsy" indie games that we're supposed to give a toss about but don't because they're crap, you know the type of person I'm talking about, people like Phil Fish.

      So all these people that really don't have much of a clue about technology but can now "create" think it's a magical new thing, something incredible and amazing.

      But in reality anyone with any degree of

    • by Anonymous Coward

      HTML (4 and earlier) was a messy complicated variant of SGML that nobody really understood and which had no compliant implementations whatsoever, but all browsers supported it well enough for day-to-day use.

      To a degree it was replaced by XHTML, which was well-understood and properly implemented across browsers, but had some practical problems for some (the requirement to load a DOM fully before even beginner to render, and the strictness of the syntax and harsh failure mode were not always considered approp

    • Back in the good old days. We had a data format that was in essence a memory dump of the system. So the data will only work with one application and sometimes on the same OS and hardware (Endianness).
      Then we started to get some open format solutions such as Postscript, LaTex which allowed for cross platform and software sharing of data. HTML got popular mostly due to it compatibility with flat text. Simple commands and the fact that you could link to an other document. This linking feature ment you could d

      • Parent's exactly right.... HTML5 is significant because it's an application development platform that runs almost everywhere. Yes, there are a lot of problems with standardization, security, semantics, etc., as others in this thread have pointed out, but none of this answers the question posed by OP... you can publish an HTML5 application today and it's instantly available to be run on hundreds of millions of phones, tablets, and PC's worldwide. That's a killer feature that no other development platform pro
      • by MSG ( 12810 )

        Back in the good old days. We had a data format that was in essence a memory dump of the system

        You mean .doc?

    • by Anonymous Coward

      Also, it comes with MAFIAA approved DRM baked into the protocol, yah oppression!

    • My understanding is that it is still just HTML, but the way some people describe it, it sounds like the second coming of C.

      It is the next coming of C.

      The moment the portable devices became web capable - and the web back then already was where most people spent their time when computing - was when the iPhone was introduced. A full-blown non-sucking modern browser on a fully mobile pocket device that the entire world wanted. That was a first. And Steve Jobs said: No,it won't run flash or any other VM. Perio

    • it's like twitter vs blogging. twitter is better than blogging because not reading your tweet is more efficient than not reading your blog.
    • I can tell you what was great about HTML 2. You didn't have a bunch of annoying shit going on in a web page.

      • I can tell you what was great about HTML 2. You didn't have a bunch of annoying shit going on in a web page.

        Apart from BLINK-tags and animated GIFs in neon colors.

    • There is nothing great about HTML. There is really nothing great about almost any modern web language/platform.

      We've been solving the same problem for the past 20+ years.
      It's all just an API

      Print text, drawing graphics, networking api, database api.

      The issue has never been about anything great, but about somehow getting this API to be supported and adopted across all devices/platforms.

      Heck, if we all used Windows, the whole web could have just been activeX controls and we'd have all had the same API as wind

    • by hey! ( 33014 )

      Well I'll tell you, from the perspective of someone who managed a development team, what the big deal is. It's managing information overload.

      Suppose you're maintaining an Android App. No problem, you just need to know Java and the Android SDK, which is very well thought out and amazingly easy to use. Oh, but now we need a server tier to our system. Well, you could learn PHP, but to keep things simple you stick with Java and go Java EE, which is not so hard to learn these days. You decide to use a REST

  • by Anonymous Coward

    Let me tell a joke. Apple in the Enterprise.

  • but... operation is not even remotely smooth enough to compete with apps running with native graphics libraries. On Apple or Android. Still too sludgy, the browser implementation still does not implement sufficient concurrency to make it work well.

    -Matt

  • If they would just have based ECMA4 on Actionscript and stuck with it, we would have had all the things we're still missing in javascript long ago. All this complaining about "proprietary" platforms is just depressing. When people complain about the need for plugin player with flash etc. and how Javascript is so much better since you don't need external players I mentally mark them down as idiots. The only difference between Flash and Javascript from running perspective is that every browser has included th
    • Actionscript is only a language just like javascript too. Its only the APIs that make Actionscript as powerful as it is. And lot of those are still proprietary.

    • by DrXym ( 126579 ) on Tuesday November 18, 2014 @05:24AM (#48409505)
      Typescript is similar to Actionscript and compiles down to Javascript. You can do stuff like interfaces, classes, inheritance, compile time typechecking etc. My experience of Typescript is the language is okay but developing it is painful because the tools are awful, particularly for someone coming from a place like Java where IDEs will give instant feedback on errors, code completion, formatting etc. Even stuff like ordering of classes can break the JS even when the TS compiles perfectly.

      I would agree with the sentiment that people who think JS (or HTML5) is some panacea for Flash are idiots. Flash was hated primarily because it was TOO popular - sites abused the fuck out of it and multi tabbed browsers sagged under the weight of so many running instances. If JS is abused the same way the performance would be just as bad.

      JS is often considered the problem, not the solution to web development. This is why coffeescript, typescript et al exit. Plus a raft of JS libraries like jquery, backbone, underscore, phantom, handlebars etc. to hide the differences or provide basic niceties that JS lacks. Plus the likes of dart, emscripten, GWT and so on which bury JS completely and spit out compiled JS. Plus the recognition from browsers that JS performance sucks and the optimization paths they've implemented (e.g. asm.js). That said, we're almost in a place where 95% of the use cases for Flash are probably achievable in JS. Personally I wish browsers would adopt PNaCl or something similar so code can be compiled and run at near native speeds - skip JS as an intermediate format when it doesn't make sense and just let sites ship bitcode.

    • ECMAScript 4 formed the basis of Actionscript 3, so there'd be no need to base ES4 on AS3!

  • How many times has it been pronounced dead ?
    Analog modems ?
    Tubes ?
    AM Radio ?
     

    • by Anonymous Coward

      How many times has it been pronounced dead ?

      Never. But as a development language it is most certainly dead. COBOL is only used in very old legacy applications invariably centered around finance and big iron. Over time it will die a natural death as companies fold, and applications are replaced on generic boxen. Redevelopment is costly, and since the Y2K effort, companies are loathed to spend huge sums of money to replace something that works perfectly fine. At some point the cost of running on obsolete hardware and the lack of skills available to sup

      • How many times has it been pronounced dead ?

        Never.

        What to say but wrong ?
        http://www.yourdonreport.com/i... [yourdonreport.com]

        Really if you haven't been around do a little searching for yourself. I have been hearing that COBOL is dead since the 80s.

        But as a development language it is most certainly dead. COBOL is only used in very old legacy applications invariably centered around finance and big iron.

        I guess you didn't know COBOL has been enjoying a resurgence ? It has a very nice niche for cloud applications, you know those CLIENT/SERVER type apps.

        http://www.microfocus.com/asse... [microfocus.com]
        http://www.zdnet.com/cobol-sti... [zdnet.com]

        Hell the COBOL 2014 standard is now out.

      • by mwvdlee ( 775178 ) on Tuesday November 18, 2014 @06:24AM (#48409661) Homepage

        The only way COBOL might die a natural death is if the biggest companies in the world all fold, without any of their IT assets being sold at liquidation.
        Given that the value of those assets is easily in the hundreds of millions of dollars for large companies, it's a bit unlikely.
        COBOL will out live anybody reading (or writing) this comment.

    • While being kept on life support by those who still care is definitely alive, I wouldn't say well for any of those. They're all in a long tail phase of life where those who still use them won't change unless forced, but basically nothing new is being done with them so the user and support bases will slowly dwindle until it truly is dead.

    • by tlhIngan ( 30335 ) <slashdot@worf.ERDOSnet minus math_god> on Tuesday November 18, 2014 @11:33AM (#48411451)

      How many times has it been pronounced dead ?
      Analog modems ?
      Tubes ?
      AM Radio ?

      I don't know about modems - they do have their uses (getting around internet censorship - interestingly because things like FidoNet generally are uncensored because they take place through phone calls). Short hauls are more likely point to point WiFi or Ethernet.

      Tubes still have a purpose - high power amplification and switching where even modern semiconductors perform poorly. If you're a radio station with even moderate power, your finals are most likely going to be a tube because high power semiconductors are not only extremely expensive, perform worse, and you'll need a lot more of them, they don't last as long and have troublesome requirements.

      AM radio also has its uses - besides being extremely easy to demodulate without a power source, AM transmissions have characteristics that are superior to FM, which is why aircraft use AM to communicate. FM communications suffer from the "capture" effect, where the strongest signal is the one demodulated by the receiver - weaker signals simply disappear. AM signals though, if you step on someone else, the receiver knows it (the receiver squeals). It's not all useless - if you have a powerful transmitter, you can still "break through" the noise to be understood (ATC towers generally transmit on the order of hundreds of watts, while an aircraft is on the order of tens of watts). However, the ability to detect a collision is extremely important and that's inherent in the AM system. FM systems don't have collision detection mechanisms and can lead to dangerous situations if someone steps in at the wrong time.

  • "Already"? HTML5 has been around for a really long time. Web devs who try to desperately hold onto flash have been losing clients for years.

    Unless, of course, this article was meant to draw attention to Tom Dale (because obviously he needs more attention), and two shitty articles about idiots thinking that web is dead. If that's the case, carry on.
  • Yes, the capabilities of browser-based apps will catch up to the desktop very soon now. We've been hearing that for a decade, and yet the browser UI toolkits are still incredibly buggy, not consistent across platforms, with many parts just flat-out poorly designed. Getting the UI of any non-trivial web app working correctly across the 5 major browsers is a fucking nightmare. But ANY DAY NOW all the problems will magically disappear-- that's a ridiculous claim, but what is worse, is all the people claiming a

TRANSACTION CANCELLED - FARECARD RETURNED

Working...