• 0 Posts
  • 89 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • 520@kbin.socialtomemes@lemmy.worldnuanceposting
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    You’re using the bear analogy wrong. If the bear analogy was about statistics, they’d choose the human because statistically speaking, many, many more people are helpful than harmful. Especially compared to a dangerous wild animal.

    People pick the bear because they themselves have been hurt too many times or have heard of people being hurt too many times. There is a perception that the bear is safer.

    That can go both ways. And often people choosing the bear can be in a vulnerable state, which the likes of Andrew Tate preys on.







  • 520@kbin.socialtoProgrammer Humor@lemmy.mlcodeStyle
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    10 months ago

    So this looks like it’s based in Java code.

    A public class means that any bit of Java code, including that injected by an attacker, can see and mess with the contents of that class.

    A private class, in contrast, means that other bits of Java code are restricted to running the class’s predefined functions.

    In theory it is supposed to help with the security of the data. In practice if an attacker gets to this point, you’ve got much bigger issues.



  • The most manual way is what C does, which is requiring the programmer to check memory safety by themselves.😛

    The difference is, Rust will throw a tantrum if you do things in an unsafe way. C/C++ won’t even check. It’ll just chug along.

    Rust is really not that harder than Java or Python.

    As someone who’s done all three, the fuck it isn’t.

    If you are familiar with C/C++ best practices to any operational level, those things will translate over to Rust quite nicely. If not, that learning curve is going to be fucking ridiculous with all the new concepts you have to juggle that you just don’t with either Java or Python.