this post was submitted on 13 Mar 2025
630 points (95.5% liked)

linuxmemes

23590 readers
51 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
    [email protected]
    [email protected]
    [email protected]
    630
    the perfect browser (lemmy.blahaj.zone)
    submitted 4 days ago by [email protected] to c/[email protected]
    179 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 0 points 2 days ago (1 children)

    I suppose we need to make definitions clearer. C++ is memory safe in the sense that you can write memory safe code. It doesn't enforce memory safety though. But not doing that is not the language's fault. If someone jumps with a bike from a flying airplane, it's not the bike's fault that they will not land safely. It's the misuse of the bike.

    saying that C++ is memory safe because it's possible to use it in a memory safe manner is like saying jumping out of a plane with the bike is safe, because it's possible to safely land (with a parachute and a lot of training).

    you always repeat that C++ is memory safe because its possible, and that "misuse" is "not its fault".
    first, you are quite simply redefining what does memory safety mean. you basically say bombs are safe because they can be safely defused with the expertise.
    second, do you really need to misuse it to get unsafe code? it does not warn anywhere. not in the instructions, not in the compiler output.
    third, its no one's "fault" that c++ is not memory safe. That's not a fault of c++. like its not a fault of factories that you have to wear safery gear when working inside because otherwise you may get injured more severely. this is just a property of C++, not a judgement

    I'd argue those weren't the best developers then.

    oh no, my suspension was correct, you are really thinking that you are the perfect coder who jever makes any mistakes. It does not make sense to argue with you

    [–] [email protected] 2 points 1 day ago (1 children)

    does not warn anywhere

    This is incorrect. If you properly test your code such errors will become visible. It's not too much of an ask to conduct systematic software testing. You should do it anyway regardless of the language used.

    you are really thinking that you are the perfect coder who jever makes any mistakes. It does not make sense to argue with you

    You are quick with being judgemental and ignoring the rest of what I said in that part, which is why I agree with you. This discussion is no longer productive.

    [–] [email protected] 1 points 1 day ago

    This is incorrect. If you properly test your code such errors will become visible.

    Ah, just as all the memory-mishandling related security issues in all operating systems out there. Nobody tests their shit well enough nowadays!

    You are quick with being judgemental and ignoring the rest of what I said in that part,

    Quick??? Read all your other comments man! I take it as you not wanting to accept it.