Comments by "MrAbrazildo" (@MrAbrazildo) on "C Is Not A Language Anymore" video.

  1. 9:20, it has the int8-to-platform-size_t as the precise integer. But if that doesn't need to be precise, and even more, 1 wants to make the app "future proof", a long will target the platform size, so that it'll keep being "upgraded" as platform size grows. It can even become faster throughout time, if the app was thought to make binary operations on 1 variable, if that is faster. long long then it's what it seems, twice the size, if allowed. short for the smallest or at least smaller than the middle 1, int. 12:23, cringe moment: I don't know what's this May 9th. 15:04, not all platforms allow this double the size. So something like int128_t is meant for a compiler error if not supported. long long means "the maximum possible signed size". So, if not supported, it may be shrinked back to 64 bits, since the user didn't express necessarily 128 bits.
    2
  2. 29:35, for that there's long (somewhat around intmax). int is the middle, and short for something shorter than int. I think this is nice: it's respecting the "imprecise" nature of many apps. 29:53, this means your app wouldn't make sense with anything else than 64 bits. But it's more common to take advantage of a "growing type throughout time". For that long is recommended. It won't break older versions, since is the same code, just using less bits. You can also use int_least64_t, from stdint.h, for at least (granted) 64 bits.
    1