• 0 Posts
  • 6 Comments
Joined 2 个月前
cake
Cake day: 2025年10月2日

help-circle
  • I do think there’s a meaningful distinction to be made between something being attributed to a real person and a fictional character being loosely based on real people, though. Like, I think we can be pretty confident that the events in the Epic of Gilgamesh didn’t really happen (at least not literally), but if Gilgamesh was, like is generally accepted, a real person, the Gilgamesh in the Epic is most likely supposed to be that guy. Whereas Robin Hood was probably never meant to be any particular person.

    That said, do we actually know whether all the stories in the Bible about Jesus were originally about the same individual? The new testament was written decades and centuries after the death of historical Jesus, by people who didn’t even live in the region, right? So all the stories the authors heard would have come from traders and missionaries of Christian cults with vocal traditions. That alone is very long game of telephone, but I imagine every town at the time would have at least one person claiming to be messiah, and if one of them became a big enough deal that rumours around him spread beyond town, there would also be bunch of copycats. So a lot of room for mix-ups.

    “I am Jesus, your king!” “I heard Jesus was buried like three days ago!” “I uh- I have come back from the dead!” And then he skipped town ASAP.



  • If you’re directly interacting with any sort of binary protocol, i.e. file formats, network protocols etc., you definitely want your variable types to be unambiguous. For future-proofing, yes, but also because because I don’t want to go confirm whether I remember correctly that long is the same size as int.

    There’s also clarity of meaning; unsigned long long is a noisy monstrosity, uint64_t conveys what it is much more cleanly. char is great if it’s representing text characters, but if you have a byte array of binary data, using a type alias helps convey that.

    And then there are type aliases that are useful because they have different sizes on different platforms like size_t.

    I’d say that generally speaking, if it’s not an int or a char, that probably means the exact size of the type is important, in which case it makes sense to convey that using a type alias. It conveys your intentions more clearly and tersely (in a good way), it makes your code more robust when compiled for different platforms, and it’s not actually more work; that extra #include <cstdint> you may need to add pays for itself pretty quickly.




  • Here’s a thought: instead of fighting this, make it a requirement to publish the prompts before making a speech. Speeches by politicians being low in information density is nothing new, and the usage of LLMs will undoubtedly make that worse, but it also means that they had to have written a terse description of the information they want to convey. If that were public, people could just read that and not waste time listening to speeches.

    It would be ironic if the first use-case for LLMs that creates positive value for society involves ignoring its output, though.