Slashdot Mirror

← Back to Stories (view on slashdot.org)

Zuckerberg: Betting On HTML5 Was Facebook's Biggest Mistake

Posted by Soulskill on from the passing-on-the-mega-death-ray-may-have-been-wrong-too dept.

An anonymous reader writes "Speaking yesterday at TechCrunch Disrupt, Facebook CEO Mark Zuckerberg acknowledged that the company's stock performance was disappointing. He also made an interesting remark about Facebook's development efforts over the past couple of years: 'The biggest mistake we made as a company was betting too much on HTML5 as opposed to native. It just wasn't ready.' According to Mashable, 'the benefits of cross-platform development weren't enough to outweigh the downsides of HTML5, which pulls in data much more slowly than native code, and is much less stable. ... Now, Zuckerberg says, Facebook is focused on continuing to improve the native mobile experience on iOS, as well as bringing a native app to Android.'"

1 of 290 comments (clear)

  1. What all us old Flash folk laugh about... by PortHaven · · Score: 1, Flamebait

    HTML5 - it's the holy grail!!!!

    Truthfully, the more and more I hear, the more and more #fail seems to be laid at HTML5's feet.

    It's immature, and poorly conceptualized. Let me just simply say, it's bad design mojo. And truthfully, if so many Slashdotters actually LOOKED at where Flash and Flex were headed, they'd see it was going in a far far more intelligent direction than HTML5.

    Consider this, what's the difference between a radio button and a checkbox? Usually, in HTML, one is a select one, and the other is a select any. But the truth is, that there should not be the distinguishment there. And often, HTML developers are forced to recreated radio button behavior with checkboxes for clients or go into elaborate styling of radio buttons. Essentially, recreating the objects. What about lists? Selectbox, multiselect box.

    Is there ANY difference between a radio and selectbox, a list of checkboxes and a multiselect box?

    NO!!!!

    Simply have a list item, and then define whether it is multiselect. All the styling and visual presentation should be separate.

    The truth is what is really being utilized is a select list, or multi select list. The display should be separate from the model (basic rudimentary MVC concepts here). Does HTML/HTML5 do this? Nope, but in fact Flex was going in this direction. Rather than add tons of new input types like the bassackward HTML5 standard did. Flex was in f