Comments by "Toby" (@toby9999) on "Branchless Programming: Why "If" is Sloowww... and what we can do about it!" video.

  1. LOL, it won't.
    1
  2. I have heard if it and I have used it in chess engines where every clock cycle counts. For instance, bitboards and branchless algorthms.
    1
  3. Nope.
    1
  4. You're stating the bleeding obvious, which is to not optimise too early. But what is too early? The later one leaves it the harder it becomes, and the easier becomes to introduce bugs. When developing high performance software, optimisation should be in the forefront of one's mind before writing any code. It should be part of the design process.
    1
  5. I doubt Python does any optimisations given how slow it runs.
    1
  6. What bad advice? The concepts presented here are very good, and they have been used in high-performance software for decades. I've used them in my chess engine, as have others, and I'm using them in a compiler project I'm working on for a propriatory language. Roughly a 50% performance increase across a set of 20,000 unit tests just by eliminating 'if' statements. Perhaps your comment was sarcasm, but yes, there's plenty of bad advice, but the bad advice is all in the comments.
    1
  7. No.
    1