Scribd Logo
Upload

Welcome to Scribd!

  • Test Odt

    Uploaded by

    Amit Patra
    31 views1 page
    The document discusses a limitation in the Dalvik virtual machine that required Facebook developers to work around. While the author criticizes Facebook, the limitation was likely due to reasonable decisions by Google developers given hardware and legacy constraints that sometimes require pragmatic solutions rather than ideal abstractions.

    Original Description:

    test.odt

    Original Title

    test.odt

    Copyright

    © © All Rights Reserved

    Available Formats

    ODT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses a limitation in the Dalvik virtual machine that required Facebook developers to work around. While the author criticizes Facebook, the limitation was likely due to reasonable decisions by Google developers given hardware and legacy constraints that sometimes require pragmatic solutions rather than ideal abstractions.

    Copyright:

    © All Rights Reserved
    Download as ODT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    31 views1 page

    Test Odt

    Uploaded by

    Amit Patra
    The document discusses a limitation in the Dalvik virtual machine that required Facebook developers to work around. While the author criticizes Facebook, the limitation was likely due to reasonable decisions by Google developers given hardware and legacy constraints that sometimes require pragmatic solutions rather than ideal abstractions.

    Copyright:

    © All Rights Reserved
    Download as ODT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    There's a weird and arbitrary limitation in Dalvik, and the Facebook guys needed to work around it.

    The author makes it sound like it's some horrible sin. How about shaming the Google developers
    who thought 6k methods was enough !or anyone" #ouldn't be good proper either, because they
    probably had a good reason !or it.
    $o!tware development isn't always stacking neat abstractions on top o! each other. $ometimes you
    have real hardware and real legacy and you %ust got to deal with it, one way or another.

    You might also like