this post was submitted on 31 Mar 2025
557 points (96.2% liked)

linuxmemes

24211 readers
1393 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, no politics, no trolling or ragebaiting.
  • 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
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 16 points 3 days ago (1 children)

    It Makea da program go BRRRRRRRR

    load more comments (1 replies)
    [–] [email protected] 19 points 3 days ago

    a low level language that has really nice features when compared to c and c++, but honestly i find it difficult to read. probably my lack of experience with it, tho.

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

    Other metals can corrode as well. It's not only iron oxidation.

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

    We're talking about rust, not corroding. Rust is only iron, nothing else.

    [–] [email protected] 1 points 2 days ago

    Can you make me some sake?

    [–] [email protected] 18 points 3 days ago (3 children)

    The very fast map in Call of Duty.

    load more comments (3 replies)
    [–] [email protected] 4 points 2 days ago

    The red part of old metals, lick it!

    [–] [email protected] 11 points 3 days ago

    It's a type of fungus.

    [–] [email protected] 11 points 3 days ago (1 children)

    Programming language like many others It has some fancy borrow checker that makes memory usage get statically analyzed by the compiler, so you dont have to manually manage memory, and the program won't need a garbage collector

    [–] [email protected] 25 points 3 days ago* (last edited 3 days ago) (2 children)

    so you dont have to manually manage memory

    Not sure how this got upvoted with this glaring mistake. You have to manage memory. The point is that the compiler catches it if you make a memory management mistake, making things like data races, uses after frees, etc. literally impossible (short of intentionally using the unsafe tag).

    [–] [email protected] 16 points 3 days ago (1 children)

    I think it's debatable whether RAII should be called "memory management". Whether dealing with Rust or modern C++, you don't need to "manage" the memory beyond specifying a container that will determine its lifecycle behavior, and then you just let it drop.

    You could certainly choose to manage it more granularly than that in Rust or C++, but in the vast majority of cases that would be considered bad practice.

    That's a qualitatively different user experience than C or pre-2011 boostless C++ where you actually need to explicitly delete all your heap allocations and manually keep track of which pointers are still valid. Lumping both under "memory management" makes the term so broad that it almost loses its significance.

    [–] [email protected] 11 points 3 days ago

    Yeah, as I understand, in the terms of language design theory, it is technically still "manual memory management". But since you don't end up writing malloc() and free(), many refer to it as "semi-automatic" instead, which certainly feels more accurate.

    load more comments (1 replies)
    [–] [email protected] 8 points 3 days ago* (last edited 3 days ago)

    Not what, who. He's the protagonist of True Detective S1.

    load more comments
    view more: β€Ή prev next β€Ί