22nd Century C
I&#x27;ve spent two decades writing C and C++, but the last 8-9 years in really high-level languages (Ruby, Javascript, Python).  From either end of the spectrum, I&#x27;ve never felt the need for such emphasis on fixed-sized numeric types.<p>I&#x27;ve commonly needed <i>access to</i> fixed size numerics, like when sending texture formats to the GPU, defining struct layout in file formats and network protocols, but I have never once thought: &quot;You know what, I&#x27;d like to make a decision as to the width of an integer every time I declare a function.&quot;<p>&quot;Just has to work&quot; low level code was the norm during the 16-bit to 32-bit transition, so it was a fucking pain.  Notice how smooth the 32-bit to 64-bit transition went? (and yes, it was smooth.)  I credit that to high-level languages that don&#x27;t care about this stuff, and people using better practices like generic word-sized ints and size_t&#x27;s in lower level code.  Keep that stuff on the borders of the application.<p>I&#x27;ve noticed a decent-sized emphasis on type size in both Crystal and Swift, two not-entirely braindead newer languages.  I don&#x27;t get it, it&#x27;s a big step backward.