Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.

14 Years of Mark Zuckerberg Saying Sorry, Not Sorry

posted by fyngyrz on Wednesday April 11 2018, @06:06PM   Printer-friendly
from the mark-down-mark-up dept.

canopic jug writes:

The Washington Post has a retrospective on 14 years of Mark Zuckerberg saying sorry, not sorry:

From the moment the Facebook founder entered the public eye in 2003 for creating a Harvard student hot-or-not rating site, he's been apologizing. So we collected this abbreviated history of his public mea culpas.

See also:
Why Zuckerberg's 14-Year Apology Tour Hasn't Fixed Facebook.

Original Submission

 
This discussion has been archived. No new comments can be posted.
14 Years of Mark Zuckerberg Saying Sorry, Not Sorry | Log In/Create an Account | Top | 58 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by Wootery on Thursday April 12 2018, @11:59AM (1 child)

    by Wootery (2341) on Thursday April 12 2018, @11:59AM (#665863)

    What secret sauce do they have that outperforms the JavaScript engines from Google/Mozilla/Apple?

    I'm not seeing anything like a Facebook JavaScript compiler from a quick web search - what's it called?

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 3, Informative) by TheRaven on Friday April 13 2018, @07:37AM

    by TheRaven (270) on Friday April 13 2018, @07:37AM (#666352) Journal

    What secret sauce do they have that outperforms the JavaScript engines from Google/Mozilla/Apple?

    Different optimisations for different use cases. Their code all uses one (apparently, very flexible but pretty terrible for performance) framework and so is all written in a specific style. Most JavaScript engines have to deal with code from a variety of different sources and care about geomean performance across a large range of benchmarks. Facebook's has to deal with code from a single source and cares about performance for that one codebase. This lets it do a bunch of things that aren't worth the effort for anyone else, because most code doesn't do the stupid things if they care about performance (see previous point about Facebook hiring cheap developers), and it can skip things that other VMs do that optimise cases that are common in general but not in their codebase.

    I'm not seeing anything like a Facebook JavaScript compiler from a quick web search - what's it called?

    I don't think they distribute it. One of my students worked on it before he came to do an MPhil.

    --
    sudo mod me up