• 6 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • qwertyasdeftoEthosLab@lemmy.caanybody here?
    link
    fedilink
    English
    arrow-up
    5
    ·
    11 months ago

    Hermitcraft? Seems hard seeing as the subreddit is about as official as it can get short of being literally, officially run by the Hermits. I can’t imagine a Lemmy community would see any significant amount of participation except for some number of people double-posting in both. I’d be happy to be wrong though.


  • I don’t think Turing-completeness implies omniperiodicity. I’m imagining a cellular automaton which follows Game of Life rules on even-numbered generations and does nothing on odd-numbered generations, which is trivially Turing-complete because it’s just Conway’s Game of Life if you ignore every other generation, but also trivially has no odd-period oscillators.


  • Going by the example in the Github, it looks like a right-to-left Lisp with Arabic keywords. Does that fully describe the language or is there more to it than that?

    I’d be interested in hearing about the parts that are more influenced by Arabic than Scheme. Are there any beyond the keyword language and writing direction? Like a new keyword that does something useful but has no equivalent in Scheme because the concept isn’t easily expressed by an English keyword?



  • Hey, I like checked exceptions too! I honestly think it’s one of Javas’s best features but it’s hindered by the fact that try-catch is so verbose, libraries aren’t always sensible about what exceptions they throw, and methods aren’t exception-polymorphic for stuff like the Stream API. Which is to say, checked exceptions are a pain but that’s the fault of the rest of the language around them and not the checked exceptions per se.



  • I might buy more from Epic if their launcher weren’t So. Freaking. Slow. Even claiming the free game is such a chore that I can’t be bothered to do it. It takes several minutes to load, responds sluggishly, and lags everything else on my computer the whole time it’s running. The only game I play from them anymore is Celeste because I can start it without ever going through the launcher.










  • The one case where I prefer video is when I know next to nothing about the topic and the other choice is mediocre to low-quality writing. Most people aren’t great technical writers, and it’s easy to skip over steps either because the writer assumes too much prior knowledge or simply because it takes effort to put that information in. On the other hand, videos are the opposite where it takes effort to cut stuff out, so you usually get all the steps which is what I need when I don’t know anything.

    If I have the option of a well-written, step-by-step tutorial though, or if I already know the topic and have a vague idea of what I’m looking for, then text is much better for being able to search/skim/go back and forth at my own pace.


  • I consider YabaIRyS more of an epithet than a nickname. I can’t imagine anyone using it to replace her name like “I wonder what YabaIRyS (IRyS) is doing”, only as a description replacing yabai like “Bruh, YabaIRyS (yabai)” in response to something she did/said.

    Forgetting Faufau is pretty indefensible. It’s been a long time, but that puts it in the same boat as Kronini and Sanana which I did remember.

    I wasn’t sure if Fuwa-chan and Moco-chan count as nicknames or if they’re just how you say their names in Japanese. I guess dropping the last syllable is what makes it a nickname as opposed to just their real name + Japanese honorific?







  • The behavior is defined; the behavior is whatever the processor does when you read memory from address 0.

    If that were true, there would be no problem. Unfortunately, what actually happens is that compilers use the undefined behavior as an excuse to mangle your program far beyond what mere variation in processor behavior could cause, in the name of optimization. In the kernel bug, the issue wasn’t that the null pointer dereference was undefined per se, the real issue was that the subsequent null check got optimized out because of the previous undefined behavior.