• 0 Posts
  • 13 Comments
Joined 2 years ago
Cake day: November 26th, 2023


  • Why not couch the article as “a vulnerability was found and patched” instead of “something bad could have happened”?

    “STORE COULD HAVE BEEN ROBBED!! A bystander noticed the door wasn’t locked, with the owner realizing he hadn’t been locking it correctly. There is no evidence anyone broke in.”

    News in the porcelain village in Oz.



  • Why do you think China has a social score? If you look up information on it, you find many scores / systems for different domains. Or how national policy and local policy can be different or at odds. You see China announced it in 2014 and barely put out a draft in 2023. The “trustworthy” score is tied to fraud, cheating people, selling counterfeits, etc. One local government is apparently trying to tie blood donation to financial breaks. Like giving you a tax break. Just an example of how the national policy can be interpreted and used in practice.

    The idea of our governments scoring us for every little tic is scary, but the danger of overreach is different than “in China, your social score goes down for not smiling.” What exactly are people referring to?


  • I need to try windows again. I remember it being more complex than Linux. I switched just so things were easier. Cygwin! Registry editing! Getting a Microsoft degree just to edit my desktop menus. I didn’t just sit there and install my programs like a good kid and actually wanted to, you know, do things with my computer. And boy did windows hate me for it.

    I’m hoping modern IDEs or just having Linux on standby would make Windows simple enough to use.




  • It’s new to me, I think it’s saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.

    It’s atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.

    It’s immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.

    It’s like the concept of flatpaks + structured system defining + modern common sense OS operations?



  • You use lifetimes to annotate parameters and return values in order to tell the compiler about how long things must last for your function to be valid. You can link a specific input with the output, or explicitly separate them. If you don’t give lifetimes the language uses some basic rules to do it for you. If it can’t, eg it’s ambiguous, then it’s a compile error and you need to do it manually.

    It’s one of the harder concepts of rust to explain succinctly. But imagine you had a function that took strA and strB, used strB to find a subsection of strA, and then return a slice of strA. That slice is tied to strA. You would use 'a annotation for strA and the return value, and 'b for strB.

    Rust compiler will detect the lifetime being shorter than expected.


    Also, ownership semantics. Think c++ move semantics. Only one person is left with a good value, the previous owners just have garbage data they can’t use anymore. If you created a thing on the heap and then gave it away, you wouldn’t have it anymore to free at the end. If you want to have “multiple owners” then you need ref counting and such, which also stops this problem of premature freeing.


    Edit: one more thing: reference rules. You can have many read-only references to a thing, or one mutable reference. Unless you’re doing crazy things, the compiler simply won’t let you have references to a thing, and then via one of those references free that thing, thereby invalidating the other references.