this post was submitted on 13 Mar 2025
617 points (95.4% liked)

linuxmemes

23532 readers
292 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    617
    the perfect browser (lemmy.blahaj.zone)
    submitted 1 day ago by cqst@lemmy.blahaj.zone to c/linuxmemes@lemmy.world
    166 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] dreugeworst@lemmy.ml 3 points 1 day ago (1 children)

    sure, maybe, but performance doesn't matter for deciding if a language is memory-safe or not. And C++ isn't memory-safe by any commonly used interpretation of that word.

    You may of course decide that the downsides of memory-safety aren't worth it for your use-case, that is a separate issue

    [–] Zacryon@feddit.org -1 points 1 day ago (3 children)

    I think it boils down, how we define "memory safe". C++ is perfectly memory safe, if you know what you're doing. A lot of people don't. Which is why Rust was born. that doesn't make C++ a memory-unsafe language. It just demands more responsibility from the user. A design philosophy that comes with a lot more flexibility than Rust can offer.

    Which is fine. Both languages have their perks. But saying C++ isn't memory safe, while Rust is, is in my opinion just plainly wrong. Besides, with "unsafe" Rust inherently already the door for memory issues.

    Modern C++ practises and dev patterns can handle most memory issues in C++ pretty easily. Consider smart pointers for example, or RAII.

    It's not the language's fault if it is used wrong.

    [–] dreugeworst@lemmy.ml 1 points 16 hours ago

    Which language would you say is not memory safe then? Is there any serious language out there where you should expect memory issues if you don't make any mistakes?

    [–] lolcatnip@reddthat.com 1 points 1 day ago

    If the standard is "you know what you're doing and never make mistakes", then all languages are memory safe. All you're doing is arguing against memory safety as a concept by redefining the term in such a way that it becomes meaningless.