• 6 Posts
  • 753 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle
  • SwingingTheLamp@midwest.socialtoLefty Memes@lemmy.dbzer0.comGig economy
    link
    fedilink
    English
    arrow-up
    42
    arrow-down
    1
    ·
    24 hours ago

    I read it as cutting through the spin. We use contemporary words like overnight oats, instead of words like gruel that have strong connotations of poverty, for essentially the same food, to obscure the fact that we are the same working class as medieval peasants were. There’s nothing wrong with gruel; and we’re just not as far removed from peasantry as we’ve been led to believe.









  • No, that’s not it, we’re measuring in incredulity units, which are syllables.

    “One hun-dred and se-ven?!” == 6 syllables

    “For-ty one?!” == 3 syllables

    Also, the first one has more vowel sounds to really draw out to indicate higher levels of I-can’t-even. It sounds only golly-jeepers in Celsius, and much more I’m-so-done-with-this-shit in Fahrenheit.



  • Scenario: I want to call a friend in Bulgaria. It’s 11:23AM GMT. What’s he likely to be doing right now? With timezones, I can quickly calculate that it’s 2:23PM local time, and intuitively know. Without, I’d have to look up a timetable of daily activities in Sofia.

    I guess if I called regularly, I could memorize the timetable, or maybe roughly calculate an offset in hours to add or subtract from GMT to intuitively relate his schedule to mine. For example, my dinner time is about 11PM GMT, so his dinner time is about 7AM GMT.

    But, I wonder, if I went there to visit, would it be easier to memorize the local timetable, or just do the math when I check the time?








  • Case-sensitive is easier to implement; it’s just a string of bytes. Case-insensitive requires a lot of code to get right, since it has to interpret symbols that make sense to humans. So, something over wondered about:

    That’s not hard for ASCII, but what about Unicode? Is the precomposed ç treated the same lexically and by the API as Latin capital letter c + combining cedilla? Does the OS normalize all of one form to the other? Is ß the same as SS? What about alternate glyphs, like half width or full width forms? Is it i18n-sensitive, so that, say, E and É are treated the same in French localization? Are Katakana and Hiragana characters equivalent?

    I dunno, as a long-time Unix and Linux user, I haven’t tried these things, but it seems odd to me to build a set of character equivalences into the filesystem code, unless you’re going to do do all of them. (But then, they’re idiosyncratic and may conflict between languages, like how ö is its letter in the Swedish alphabet.)


  • One can define mass shooters as mentally ill. It’s not exactly wrong, but not useful in the slightest, since you can only make that kind of diagnosis retrospectively. So what? The victims are already dead. To the point, mental illness is useless as a prospective indicator of potential mass shooters, since the vast majority of people with mental problems do not become one.