Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TR
Posts
0
Comments
334
Joined
2 yr. ago

  • Nuclear is unexpectedly safer and less polluting than renewables. That's including stuff like Chernobyl. Also less expensive overall. The plant itself is expensive yes but for the energy output/cost per watt it's by far cheaper last I checked.

  • It produces extremely long-lasting waste, on timescales humans are not equipped to deal with.

    Very little waste compared to burning coal or oil which also produces waste we aren't equipped to deal with. See oh idk global warming.

  • I'd probably say it depends but I'm no Rust expert and I have no direct experience with C (though quite familiar with C++).

    Basically I'd expect writing C to be easy, but not safe. IE you can quickly and easily write C that compiles but has runtime issues. Rust for the most part will catch everything but logic issues during/before compilation meaning once the program runs you'll have very high confidence in it's runtime behavior leading to time spent "fighting the compiler" instead of figuring out wtf is going wrong at runtime.

  • What Rust provides is statically guaranteed memory safety. Some C++ types will prevent memory issues however the language itself is unsafe. Playing with raw pointers is just as valid as using std::unique_ptr. In Rust however you must sign a contact (using unsafe) in order to play with raw pointers. Unsafe is you the programmer promising that you followed the rules. This is like how C++ says it's illegal to write UB and your program will break (and it's your fault) but enforced through a special type of block

  • Yes Rust is harder to write than C, that's basically by design as it's due to the statically guaranteed memory safety. That's pretty magical. C doesn't have that and neither does C++ even with smart pointers and such. Rusts unsafe keyword is poorly named, what it actually does is tell the compiler that you the programmer guarantee Rusts rules are upheld within the unsafe block.

    For example

    Access or modify a mutable static variable

    That is a global, that's incredibly hard to impossible to statically prove it's safely done, so you have to do it in an unsafe block. So you violating Rusts rules within an unsafe block is actually using the unsafe block wrong. That's not what it's for

  • Unsafe Rust really just let's you play with pointers

    This is the entirety of what Unsafe Rust allows

    • Dereference a raw pointer
    • Call an unsafe function or method
    • Access or modify a mutable static variable
    • Implement an unsafe trait
    • Access fields of unions
  • Brave (yes I'm aware ya'll don't need to yap at me).

    Yep seriously Brave all on its own blocks YouTube ads and no performance issues (likely thanks to being Chromium based).

    To address some complaints about Brave you can uh turn that stuff off. I don't like Crypto so I... have all of that junk disabled. Doesn't bug me whatsoever. Opt in ads (for their stupid crypto coin) are disabled by default (or least where when I installed). And the CEO is a bad person (surprising I know)

  • When it's easier to think about a system in terms of objects. The classic example is video game Entities/Game Objects. GUI stuff has also been very pleasant with OOP as buttons and the like are all easily conceptualized and worked with when seen as objects.

  • I fundamentally believe what Apple has become is the inevitable consequences of a company being successful under capitalism. For one thing we see this with all of them not just Apple. Apple just goes to excessive lengths to fuck people over for a couple extra bucks