Execution Speed is Deprecated, Use Python!

Developer time is the most valuable resource. Writing in Python may cause slower code, but it is in reality much more efficient because you will get an exponential amount of more work done!

>>33
stdbool is pointless bullshit created to appease C++ programmers.  It just adds some extra typedefs for ``comfort'', the actual semantics of true and false values are the same regardless of whether stdbool is used or not. Case in point:

#include <stdbool.h>
...
bool x = 2; /* valid C code */

if (x) {
        /* test succeeds */
}

if (x == true) {
        /* test fails */
}

If you aren't working on a mixed codebase there is less than zero reason to use stdbool.

>>34
Yeah, because big endianness and ternary are such great ideas. IHNBT

>>39
P4 processors did not have a barrel shifter
Really? They couldn't spare the transistors for that of all things? Terrible!

the ALU was pipelined so that operations <= 16 bits of data were around twice as fast as those needing 32 bits.
Wow. Did the designers really think people would actively take advantage of this?

Very sensitive to instruction and data alignment, not unlike most RISCs.
Except that on RISC, one generally assumes that operations using the machine's native word size will be fast.