561
submitted 1 week ago by Gormadt to c/linuxmemes@lemmy.world
top 50 comments
sorted by: hot top controversial new old
[-] JayDee@lemmy.sdf.org 4 points 5 days ago

Something that deteriorates the structural integrity of load-bearing frameworks /s.

Being serious, it's another programming languages that is gaining popularity. Others can expand on why it's good. I've never used it myself so I can't comment in good faith. I also don't have any experience with Rust-bros so I can't comment on their code quality. I've mostly just been watching amused as they fight with the Linux development community.

[-] InternetCitizen2@lemmy.world 155 points 1 week ago

Iron Oxide. Everyone else is wrong.

[-] LadyMeow 38 points 1 week ago
[-] remotelove@lemmy.ca 48 points 1 week ago* (last edited 1 week ago)

Wustite, ferrous oxide, is black. FeO.

Typical rust, usually found as hematite, is Fe2O3 and is red/brown. Also an iron oxide.

Magnetite is also another black iron oxide, Fe3O4.

There are quite a few other flavors of iron and oxygen too.

[-] dan@upvote.au 27 points 1 week ago

flavors of iron

Yum yum

load more comments (1 replies)
[-] Upperhand@lemmy.world 118 points 1 week ago

It's a brutally competitive and toxic game.

[-] TheAgeOfSuperboredom@lemmy.ca 16 points 1 week ago

You must be looking for /c/playrust

load more comments (1 replies)
[-] Ephera@lemmy.ml 108 points 1 week ago* (last edited 1 week ago)

It's a programming language, which is particularly relevant for Linux, because it doesn't require a runtime (separate program that runs the code). This allows it to be used in the kernel.

But it also means that it's very good for building libraries. With a small bit of extra work, virtually any other programming language can call libraries implemented in Rust (like you can with libraries implemented in C).
Add to that, that Rust allows for performance similar to C and makes lots of typical C bugs impossible, and suddenly you've got folks rewriting all kinds of C libraries and applications in Rust, which is something you might have also heard about.

load more comments (4 replies)
[-] captain_aggravated@sh.itjust.works 100 points 1 week ago

Actual answer:

Rust is a relatively new programming language. Similar to C or C++ it compiles directly into executable binary code so it can be used for bare metal or low level operating system programming. It is thus relevant to Linux kernel development as things like drivers can and are being developed in Rust.

Compare this to the likes of Java or C# which get compiled to bytecode or a kind of pseudo machine code that gets run in a virtual machine, which has advantages for application development, or something like Python which is interpreted (or just-in-time compiled) at run-time, useful as an end user scripting language.

Rust is designed from the ground up to tackle some modern problems, a key one being memory safety. It's a lot more paranoid about memory allocation and access and it's structured around this. Older languages like C allow the programmer a lot more absolute control over the hardware, which effectively means the C programmer has a lot more footguns in his toolbox. Theoretically, Rust offers fewer opportunities for the developer to shoot himself in the foot.

Rust also comes with some really cool tooling. Compiler errors usually point straight at the problem and say something like "Shouldn't there be a colon here?" The build system, called Cargo, is really slick in a lot of ways, handling linking, compiling, even library package management in a very automatic fashion. It's real slick to work with.

As with anything, fans of the language can be a bit much; they stereotypically suggest rewriting everything under the sun in Rust whether it makes sense or not, and this includes the Linux kernel, which has caused some friction in the community; Linux contributors are often very accustomed to C and some don't want to deal with anything else.

[-] Bogus007@lemm.ee 14 points 1 week ago

I like the description by a Finn who said: Rust is like a car with automatic, while in C (or Zig) you need to change the gears. In Rust you literally follow the compiler, which allows many young developers to program at low level, while C demands more time to avoid bugs. It is up to each person what he/she prefers. I would prefer to control myself the stuff and learn the in and outs of memory management.

[-] itslilith 19 points 1 week ago

It's fair to want to learn (and it's certainly a good skill to have), but the question is what you'd rather see in a large, production environment. Guard rails are usually there for a reason. As for the control: you actually can program memory-unsafe (and in kernel development you often have to!) in Rust. The difference is that in Rust it's explicitly marked by an unsafe block:

unsafe {
  ...
}

That way you get the same, fine-grained control over low-level processes, but someone else reading your code can at a glace spot where potential memory bugs may be.

In the end, languages are a tool. Especially for personal projects, everyone should just go with what's fun to them. I personally think it makes sense, logistically, to slowly transition legacy C-based projects to Rust, because it makes onboarding new developers easier, while keeping the same memory safety that requires years of experience otherwise, basically for free. But there's really no rush to rewrite anything that's working well in Rust

The sound bite I heard was "the unsafe keyword makes memory bugs greppable."

load more comments (7 replies)
load more comments (2 replies)
load more comments (1 replies)
[-] hedge_lord@lemmy.world 80 points 1 week ago* (last edited 1 week ago)

Rust is a programming language designed to run on crabs. It just happens to also run on computers. When rust programmers talk about the borrow checker, that's something born directly out of having to run on crabs. It's difficult to get the little guys to cooperate otherwise. And when they talk about rust having good error messages that's because of the crabs too. The compiler is not just some piece of software, it's a piece of software being run on crabs and the crabs have some measure of intuition to them. Basically what I'm saying is that carcinization applies to computer hardware.

[-] hedge_lord@lemmy.world 43 points 1 week ago

Rust is when you run DOOM on 16 billion crabs. You can't do that in other languages. Just ask Amelia Airheart.

[-] rtxn@lemmy.world 59 points 1 week ago* (last edited 1 week ago)

The bane of Intel CPUs, and a trigger word for C geriatrics.

[-] chronicledmonocle@lemmy.world 24 points 1 week ago

Back in my day we coded in assembly and we liked it that way!

[-] superkret@feddit.org 18 points 1 week ago* (last edited 1 week ago)

Back in my day I didn't code at all and I liked it that way!
(My day was today)

[-] xmclark@lemmy.world 49 points 1 week ago

It’s a 2025 movie, starring Alec Baldwin, that gained notoriety in 2021, when a cinematographer was accidentally killed by a live round fired from a prop-revolver that Alex Baldwin was using.

load more comments (4 replies)
[-] limer@lemmy.dbzer0.com 42 points 1 week ago

Rust is both a nice programming language, and an obnoxious social movement made of a small minority of Rust programmers who are very loud

[-] sunshine@lemmy.ml 62 points 1 week ago

oh I don't consider them obnoxious. I'm from Python-land, they've been saving our asses with good tooling lol. the quality of output from the rust ecosystem speaks for itself

[-] Jumuta@sh.itjust.works 20 points 1 week ago
[-] rtxn@lemmy.world 34 points 1 week ago* (last edited 1 week ago)

who are very loud

Most of the "should we or should we not" discourses/dramas I've read about were initiated or escalated by the anti-Rust crowd. They seem to be a lot more vocal (not to mention impolite) about their opinions than actual Rust developers.

[-] zea_64 10 points 1 week ago

Specifically in the Linux kernel, the 2 big reasons to use it are memory safety (huuuuggee benefit) and that a lot of younger devs like it and thus it will attract their contributions.

The only reasons I can think of to not use it are that some people want their own toolchain and having multiple languages in the kernel adds complication. But tbh, none of that justifies banning Rust stuff that realistically wouldn't have been written at all if C were the only option.

And then there's the people who show up in Phoronix, HN, Reddit, and YouTube comments saying Rust is over-hyped without showing why it's unfit for purpose and also trying to dictate what someone does with their own project. Perhaps it's something to do with the representation of queer people and other minorities in the Rust community, because otherwise I do not understand why people would be sooo passionate in hating the Rust community like the group I described above is.

load more comments (3 replies)
[-] lobut@lemmy.ca 19 points 1 week ago* (last edited 1 week ago)

That's rather rude and untrue ..... the programming language isn't at all nice! /s

ducks and runs away

[-] dan@upvote.au 18 points 1 week ago

small minority of Rust programmers who are very loud

They also list "written in Rust" as the primary feature of software they write, even though the majority of users don't care as long as it works properly.

load more comments (4 replies)
[-] ZkhqrD5o@lemmy.world 42 points 1 week ago
[-] zea_64 33 points 1 week ago
load more comments (1 replies)
[-] Agent641@lemmy.world 40 points 1 week ago

It's a survival crafting game where players help each other survive the world with mutual cooperation, kind words and absolutely no Nazi or racist behaviour.

load more comments (3 replies)
[-] HotsauceHurricane@lemmy.one 25 points 1 week ago

It’s also what this beautiful thing is written in

load more comments (1 replies)
[-] cupcakezealot 22 points 1 week ago

step one get hrt prescription

step two learn rust

step three buy socks

load more comments (2 replies)
[-] AmazingAwesomator@lemmy.world 20 points 1 week 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.

[-] jeena@piefed.jeena.net 18 points 1 week ago

The very fast map in Call of Duty.

load more comments (3 replies)
[-] DonutsRMeh@lemmy.world 17 points 1 week ago
load more comments (4 replies)
[-] polite_cat@lemmy.world 16 points 1 week ago

A type of person whos apartment would be a mess cause they never collect their garbage, but they have a good memory where they put things and what they need, so it is never a problem.

[-] AkatsukiLevi@lemmy.world 16 points 1 week ago

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

[-] TheTechnician27@lemmy.world 25 points 1 week ago* (last edited 1 week ago)

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).

[-] 5C5C5C@programming.dev 16 points 1 week ago

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.

[-] Ephera@lemmy.ml 11 points 1 week 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)
[-] frezik@midwest.social 14 points 1 week ago

It's for programmers who need their Imposter Syndrome amplified.

[-] HotsauceHurricane@lemmy.one 14 points 1 week ago

It Makea da program go BRRRRRRRR

load more comments (1 replies)
[-] ILikeBoobies@lemmy.ca 13 points 1 week ago
[-] Zacryon@feddit.org 12 points 1 week ago

It's for people who suffer from severe anxiety when they see stuff like: -> or * for example. /j

[-] SexualPolytope@lemmy.sdf.org 11 points 1 week ago

It's a type of fungus.

load more comments
view more: next ›
this post was submitted on 31 Mar 2025
561 points (100.0% liked)

linuxmemes

24335 readers
688 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