• 1 Post
  • 8 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle


  • To be honest, what I’m most mad about isn’t the typoes, it’s that someone generated this image and figured, yeah alright, that will clear things up.

    On some level you want to believe that even if someone does not come up with a proper concept for a visualization, that they still check what the AI shat out, so that it’s at the very least not conceptually wrong and not confusing.

    This image isn’t just shitty, it’s actively worse than having no visualization. They could’ve generated that, chuckled, and not used it. Just how do you blunder your perception check so badly that you decide to include it anyways?




  • Huh, so if you don’t opt for these more specific number types, then your program will explode sooner or later, depending on the architecture it’s being run on…?

    I guess, times were different back when C got created, with register size still much more in flux. But yeah, from today’s perspective, that seems terrifying. 😅


  • What really frustrates me about that, is that someone put in a lot of effort to be able to write these things out using proper words, but it still isn’t really more readable.

    Like, sure, unsigned is very obvious. But short, int, long and long long don’t really tell you anything except “this can fit more or less data”. That same concept can be expressed with a growing number, i.e. i16, i32 and i64.

    And when someone actually needs to know how much data fits into each type, well, then the latter approach is just better, because it tells you right on the tin.