Skip Navigation

    1. Performance is often more tied to the code than to the interpreter - an O(n³) algorithm in blazing fast C won't necessarily perform any better than an O(nlogn) algorithm in Python.

    An O(n³) algorithm in Python won't necessarily perform any better than an O(nlogn) algorithm in C. Ever heard of galactic algorithms?

    The overhead my classmates had dealing with poorly optimised code that caused constant cache misses was far greater than the interpreter overhead in my code (though at the time I don't think I could have explained why their code was so slow compared to mine).

    Did they write naive linear algebra operators?

  • There are decades of articles on c++ optimizations, that say "use empty() instead of size()", which is same as here.

  • Arson, murder and jaywalking

  • Scoreboard, scoreboard.

  • USA is East Alaska.

  • EUSSR, the country of healthcare and public transport.

  • Deleted

    Jerkoff

    Jump
  • USSAsians.

  • Public transport

  • W3C

  • It'd take 24 Viking women just to pick your american fat ass up off the computer chair.

  • Boycotted. Girlcotted. Everyone cotted!

  • build your own print server that gives you all the bells and whistles like AirPrint.

    ...why? CUPS is print server. You don't need anything else.

  • Deleted

    Permanently Deleted

    Jump
  • KKKGB

  • They already were wasted by making teslas

  • Then same can be said about JPEG LS and JPEG XL. Most browsers don't implement that.

  • Both og JPEG and JXL support lossless compression.

  • Deleted

    Permanently Deleted

    Jump
  • Person: makes map app for everyone to use

    Twitter baby: "Racial slurs! Racial slurs!"