this post was submitted on 13 Mar 2025
624 points (95.3% liked)

linuxmemes

23532 readers
165 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
    624
    the perfect browser (lemmy.blahaj.zone)
    submitted 2 days ago by cqst@lemmy.blahaj.zone to c/linuxmemes@lemmy.world
    173 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Zacryon@feddit.org 1 points 1 day ago (2 children)

    I've a very long track record using C++ as well and I can't share the feeling. I don't say it's alyways easy. I'm just saying that it's doable and therefore whether the software is memory safe depends on the expertise of the devs. Modern C++ practises, programming patterns and as well tools from the STL (or even your own implementation) make life a lot easier. If you don't use them, that's not the languages fault. In the end, how you use the language still matters a lot. If you'd like to think less about memory management, go on and use Rust or C# or Java or even Python if performance doesn't matter. That's perfectly fine. This can come with other issues, like more boilerplate in the case of Rust for example, but in the end those languages are tools. Choose the tool which gets your job done.

    [–] WhyJiffie@sh.itjust.works 1 points 1 day ago (1 children)

    I don't think this solely depends on the level of experience. People make mistakes, and these kinds of mistakes are very hard to find. And don't tell me you are the perfect coder that makes no mistakes, introduces no bugs.

    [–] Zacryon@feddit.org 1 points 13 minutes ago

    I'm not. But in my experience, using memory safe programming patterns, classes and possibly additional testing and analasys tools do the job quite well.

    But yeah. I changed my mind about this memory-safety-property. The lack of enforcement really does make C++ inherently memory unsafe.

    [–] lolcatnip@reddthat.com 3 points 1 day ago* (last edited 1 day ago) (1 children)

    whether the software is memory safe depends on the expertise of the devs

    No. Just stop. If a language depends on the expertise of the developer to be free of memory bugs, then by definition, it is not memory safe because memory safety means such bugs are impossible by design. Quit trying to redefine what memory safety means. A program being free of memory bugs does not in any way imply memory safety.

    [–] Zacryon@feddit.org 1 points 7 minutes ago

    Yes. I stopped now. I was hinted towards the usual definition of memory safe languages at another point in this discussion.

    Although it is perfectly possible to write memory safe code in C++, I agree that the lack of enforcement makes it inherently unsafe.