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

help-circle
  • This is how Wisconsin’s law is so fucked up: The three men he shot were not working together, were not coordinated, did not know each other. So, on the one hand, Rittenhouse may have subjectively felt under coordinated attack, he was not, but the subjective feeling is what matters for the law.

    From Huber:s POV, he was trying to disarm a murderer. Maybe he felt threatened, too? But the law is so fucked, his POV doesn’t matter because he’s dead. In Grosskreutz’s POV, he was approaching an active shooter who’d just killed two men and trying to defuse the situation. When Rittenhouse pointed his gun, Grosskreutz would have been justified under the same law in blowing him away.

    In short, the law incentivizes shooting first.









  • 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.)


  • That’s true, but our theory of physics is far more complex than those simple patterns. It actually consists of many, many interrelated theories that mutually reinforce each other. And that so many of them describe phenomena described with c as a term strongly indicates the speed of causality of pretty fundamental.

    In any case, I’d be very interested to learn how it shakes out, but I probably won’t be around in 300 years to do so!