Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Disclaimer: I pretty much don't like Rust, but most criticism of it boils down to culture war.
Got curious and looked into it. All the architectures officially supported by Debian are also supported by Rustc.
I guess if you're a fan of GNU/Hurd it might cause issues?
The art was generated by AI, and likely the content and the text. Why are you all taking this so seriously?
*Looks at community name.* Seriously?
The issue is probably the dropping of support for several obscure architectures used by 3 people combined due to there being no llvm support rust relies on
It is. But I doubt they are used by 3 combined people.
The Debian project needs to keep the machines for compiling and testing. And there's probably no other machine of those architectures available for the enthusiasts to actually use.
I don't know about rust being an issue for debian; but AI is sure an issue. Weird move
Why would a programming language destroy an operating system?
If your tinfoil is thick enough, no coherent thought can penetrate.
I think this is about how apt will depend on rust and then debian will need to drop some architetures it supports
No, no, the architectures! The Debian architecture (apparently)!
Processor architectures maybe. They put Rust into Debian and it's so bad that now e.g. amd64 is ruined forever for any OS and won't see any new processors in the future. We'll have to move to a different architecture. I didn't watch the video since I treasure my brain cells too much but that's what I choose to read into it.
(A more reasonable reading is that Debian now ships a kernel that includes Rust code and coincidentally has also dropped builds for several obscure architectures but I do not feel obliged to assume reason with a title and thumbnail like that.)
Badly chosen title and thumbnail aside. It's actually the 2nd reason. With Rust now part of the kernel, the kernel won't build for a number of architectures. Whether the architectures are obscure or not is debatable. I sure wouldn't want to debate one who still uses them though. Either way, the fact that the kernel won't be compiled for these architectures is true.
So it's not "Rust destroys Debian", it's "Rust destroys Linux"?
Partly it's more of "destroy an ecosystem". Among languages, Rust is at the frontlines of a continuing trend to remove GPL-licensed, community toolkits and put corporate-friendly, AI-friendly toolkits in their place, eg.: replacing grep with openaigrep, which would basically be step 2 in the process of privatizing or corporatizing the Linux ecosystem (and leads to the loss of a number of user freedoms).
Hopefully nobody tells the corpos that they can just use BSD if they want a MIT licensed kernel and user-land
Licenses don't matter when corpos don't care anyways. Especially for training LLMs. They don't care about copyright. I choose to use tools based on there merits over simply going "it has my favorite license." Even though I say that, I still prefer AGPL even though I understand that of the corpos want to steal, they'll steal it.
That's true, for now.
Licenses might not matter now but if enough of a communal current for respect of licenses and of punishment for license breaking ramps up, we might be able to see something like (L)GPL class action suits against large corporations, at which point it becomes possible to at least seek reparation for previous damages.
But as with anything and everything law-related, licenses are declarations of intent. Their validity is only substantiated by the holder's capacity to pursue punishment.
It's 70-80% culture war bullshit, the rest is actual complaints for the language (or at least the use of language) often bundled with culture war bullshit.
Some people just drink the cool aid and decide they have found their new Lord and savior in a programming language. Others just add a new tool to their toolbox.
And some people pretend Rust is literally Satan, because the Code of Conduct, meanwhile companies like Twitter use it, projects like Ladybird use it, etc.
The Linux Kernel uses it too. Its not a hype, and adoption is happening in real time.
I know. My main grief with it is that it should have been a memory safe language closer in looks and paradigm with C, but many of those alternatives are still new. Would have solved some of the drama surrounding Rust integration.
Can 100% agree with it. Rusts type system is very unique and quite unusual especially when coming from C
Rust is the future. Notice how the C design committees are scrambling to replicate what rust does while C continues to lay eggs everywhere it goes
It's not that I don't like Rust, I just don't know what to do with it
You use it to write programs.
Feed it through a coffee grinder and mix it with similarly powdered aluminum.
Then set that on fire (bonus points for doing it on lake ice. That’s fun!)
Oh. Uh. Not that kind of rust?
Anything you used to make in C, C++, C# and Typescript
Excuse me but, can Rust even give me undecipherable Lore Ipsums of diagnostics at the same level that C++ can? If not, it's not even a competition.
This may be cheating but yes, sometimes there are cycles in type/generic definitions and the compiler loops their identifiers over and over, nesting them inside each other
Just wrap it in unsafe tags and you can accomplish the same things you can already do in any other language!
But be noted it's really not a drop-in replacement language for C-derived languages. It's more like OCaml with curly brackets.
Yes of course. But there is nothing you can't do. Only thing that may retain some of you is tooling that wasn't ported
I am starting to learn Rust and the only reason I don't intend on using it for GUI stuff for the time being is because I just like QtWidgets a lot and GUI toolkits in Rust are a pretty new thing.
Apart from that, pretty much all logic can benefit from a language that forces people to be more explicit.
Although I won't consider it for larger projects until the borrow checker gets the overhaul it needs, because I'd rather not start hating another language.
What about the borrow checker needs an overhaul? Seems to do it's job quite well. If you want to remove it then you should use like C++ or Zig or something since the borrow checker is fairly fundemenal to the design of the language
This is second hand info, but some people have had problems in bigger projects where the borrow checker ends up rejecting valid Rust code.
I think I have seen those comments right here in Lemmy.