• 3 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2023

help-circle



  • If you can see a polar bear it’s a threat.

    They really aren’t like other bear species. They are an apex predator in an area where basically nothing other than another polar bear can even harm them. They see most things as food, including humans.

    As a bonus, Iceland has a pretty wonky ecosystem that needs protecting as is and polar bears aren’t native to the island. They have to swim extreme distances to get there, making relocation extremely difficult and expensive, plus if they leave it be it will entirely disrupt other wildlife in the area, to say nothing of the human population.

    As others have said, it sucks that it got shot, but Iceland especially has very limited options on how else to deal with it. Shoot on sight is, unfortunately, a very reasonable policy for them.






  • On the one hand, Ina would be a great roommate in that she never leaves her room.

    On the other hand, I’m pretty sure I recall a room cleaning stream in which a certain priestess basically just spent a ton of time throwing cans that were lying around into a bag, which doesn’t sound great.






  • It’s been almost a decade since I used C++ and had to verify, but after some quick searching around it looks like it hasn’t changed a ton since I last looked at it.

    You can use smart pointers, and certainly you should, but it’s a whole extra thing tacked on to the language and the compiler doesn’t consider it an issue if you don’t use them. Using new in C++ isn’t like using unsafe in rust; in rust your code is almost certainly safe unless marked otherwise, whereas in C++ it may or may not be managed properly unless you explicitly mark a pointer as smart.

    For your own code in new codebases this is probably fine. You can just always make your pointers smart. When you’re relying on code from other people, some of which has been around for many years and has been written by people you’ve never heard of, it becomes harder to be sure everything is being done properly at every point, and that’s where many of these issues come into play.


  • brenticus@lemmy.worldtoLinux@lemmy.mlLadybird announcement
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    4 months ago

    C and C++ require more manual management of memory, and their compilers are unable to let you know about a lot of cases where you’re managing memory improperly. This often causes bugs, memory leaks, and security issues.

    Safer languages manage the memory for you, or at least are able to track memory usage to ensure you don’t run into problems. Rust is the poster boy for this lately; if you’re writing code that has potential issues with memory management, the compiler will consider that an error unless you specifically mark that section of code as unsafe.




  • Honestly? Bash. I tried a bunch a few years back and eventually settled back on bash.

    Fish was really nice in a lot of ways, but the incompatibilities with normal POSIX workflows threw me off regularly. The tradeoff ended up with me moving off of it.

    I liked the extensibility of zsh, except that I found it would get slow with only a few bits from ohmyzsh installed. My terminal did cool things but too slowly for me to find it acceptable.

    Dash was the opposite, too feature light for me to be able to use efficiently. It didn’t even have tab completion. I suffered that week.

    Bash sits in a middle ground of usability, performance, and extensibility that just works for me. It has enough features to work well out of the box, I can add enough in my bashrc to ease some workflows for myself, and it’s basically instantaneous when I open a terminal or run simple commands.