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.
It’s for programmers who need their Imposter Syndrome amplified.
The very fast map in Call of Duty.
“1v1 me on Rust bro”
Ah those were the days
Does COD still have that map? The last time I played it was in MW2 on the Xbox 360.
As far as I know yes, I watched some videos where people were talking about the newest MW version and they showed that map, that’s how I remembered :D
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.
ABSOLUTELY no racism, whatsoever
Actually it’s a low budget western movie starring Alec Baldwin that resulted in the tragic killing of cinematographer Halyna Hutchins due to inadequate safety practices on set.
And no bee grenades
Fe₂O₃·xH₂O
It’s not working…
Is… Is that Rust on a phone!?
Yes. It’s an app called termux, which is like having Debian on Android
Did enable to cargo your pants in the right bucket assembly? I think you need at least 1.6.2 but not more than 2.2
Try downgrading in the computer
I am on 1.8.0
Maybe the battery is too low on the phone, and it’s also rusty?
It’s a brutally competitive and toxic game.
You must be looking for /c/playrust
deleted by creator
The bane of Intel CPUs, and a trigger word for C geriatrics.
A source of entertainment in the Linux kernel mailing list
Back in my day we coded in assembly and we liked it that way!
Back in my day I didn’t code at all and I liked it that way!
(My day was today)
What is the issue with Intel CPUs? I’m OOTL here.
Some of their 13th and 14th generation CPUs have manufacturing defects that resulted in oxidation. In some use cases (servers and such), failure rates sometimes reached 50%. https://www.youtube.com/watch?v=OVdmK1UGzGs
and they kept denying there was an issue, until there was so much proof that they couldn’t deny it any more and were like “okay fine there’s an issue so we’re going to be extra generous and extend your warranty one whole year”
They were probably trying to run out the warranty period. (for legal reasons, this is speculation)
In countries like Australia that have good consumer protection, they’d have to replace failed CPUs even outside of the warranty period, because they’ve still failed in a time frame shorter than a regular person would expect a CPU to last. The USA really needs better consumer laws.
Not what, who. He’s the protagonist of True Detective S1.
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.
It’s a multiplayer survival game in the vein of Minecraft.
That’s a nice way to put it. I call it more of a Noob Murder Simulator
Rust is iron oxide, mostly used to make thermite
Rust is both a nice programming language, and an obnoxious social movement made of a small minority of Rust programmers who are very loud
That’s rather rude and untrue … the programming language isn’t at all nice! /s
ducks and runs away
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
uv <3
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.
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.
a lot of younger devs like it and thus it will attract their contributions.
You get it! That is probably the biggest “soft” factor for why I want to see Rust proliferate. Nobody wants to learn C! It’s an ancient, cumbersome language that is difficult to use in a secure way. I’ve been both a student and an employee at a university with many programming-related classes, and beyond the absolute basics of memory management, nobody does anything in C, or even C++. It’s almost always C#, Java, Javascript, or Python. No Rust yet because most of our teachers are also geriatrics.
Linux (and FOSS in general) has an age issue. Prolific older developers are leaving their projects or transitioning to less code-focused tasks, and the ranks are not being filled. Prospective young developers simply bounce off projects because of steep entry requirements, and the active resistance of anti-Rust evangelists (the likes of Christoph Hellwig for example) doesn’t help either.
having multiple languages in the kernel adds complication.
which is why we should simply rewrite the whole kernel in rust. boom problem fixed 😎 /j
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.
It matters to potential contributors. It’s also a floating signifier for a lot of things.
The majority of users aren’t contributors though. It’s fine to mention it in contributor documentation but I find it weird to advertise it as an end-user feature given most apps written in other languages don’t do this.
It’s also a floating signifier for a lot of things.
Like what
A program being written in rust itself doesn’t guarantee anything, but it tells you what you’ll probably find:
- Utf-8 support
- No shenanigans with installations, dynamic libraries and such. Just download and execute.
- Multi-platform support
- Low resource usage.
- semver.
- Compile with just 1 command if you want to.
- MIT/apache2 license.
- No memory leaks.
- If it crashes, at least it will probably log out something more helpful than “SEGFAULT”.
Many of those are highly positive to the end consumer.
It’s a type of fungus.
Water? Like, in the toilet??
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
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
unsafetag).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.
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()andfree(), many refer to it as “semi-automatic” instead, which certainly feels more accurate.
