174
Debian's APT Will Soon Begin Requiring Rust: Debian Ports Need To Adapt Or Be Sunset
(www.phoronix.com)
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
Is it just me, or does that seem .. abrupt?
There's time until March for the maintainers of the 3 niche architectures to organize and make rust available for them. Doesn't sound that abrupt to me
For small niches, six months can be rather aprupt.
My niche can take 5 days or 5 months, depending on ADHD
Wasn't there a Rust-to-C compiler that would circumvent this limitation?
Yes. There is also a GCC front-end for Rust (does not go to C first).
The timeline is not super abrupt, especially for architectures where all he is asking is to ensure that your Rust toolchain is in order. That is especially true when you consider that Rust is already well maintained on all the Debian architectures that people actually use.
The abruptness (almost rudeness) is in the second part where he basically says that, if you cannot get Rust going in time, you should just stop releasing Debian for that architecture.
It is mostly just poorly worded though. Because none of these architectures have “official” support even now. This will not be the only way they are behind. So, there is not reason to be so dramatic.
And that would be my response to him. Another option here is that these alternative architectures just continue to ship an older version of APT for now. Emergency avoided. Few of them ship with up-to-date versions of APT even now.
Another solution is to use one of the multiple projects that is working to make Rust code build with the GCC compiler back-end. At least one of these projects has already announced that they want to work with these Debian variants to ensure that APT builds with them.
So, the 6 month timeline is a reasonable impetus to make that happen which would be quite a good thing beyond just APT.
There are many other useful tools written in Rust you are going to want to use on these architectures. It will be a fantastic outcome if this pressure from APT kickstarts that happening for some of these long abandoned architectures (by the mainstream at least).
For package maintainers, it's reasonable to expect security updates are rolled out the same week that a vulnerability is found. If you can't deploy a new version of a package in 6 months, not maintaining the package is also a valid option.
but this is not a vulnerability, but adding a cpu architecture to a programming language
Strange times.
how many compiler back doors have we seen versus use-after-free/stack overflow attacks?
The anti-Rust crowd baffles me. Maybe C++ has rotted their brain to the point they can’t “get” the borrow checker.
My only complaint is that its syntax is an ugly mishmash. Should have copied scala or f#
More like Rust has rotted someone's brain. "Hey, I can't code safely, so I will use this new toy that is supposed to make me". This line of thought is OK as long as it does not get imposed on anything I do as a programmer
The industry cannot code safely. There are many reports, studies, and corporate disclosures highlighting that memory related bugs are the primary source of critical security issues in C and C++ code. That is why even NIH companies like Google and Microsoft are adopting Rust in their core products.
That you want to publicly ignore all that evidence to paint it as an individual skill issue does not come across as competent or intelligent. Few of us are going to assume your code is free of these kinds of bugs.
The fact that your have to say it so dismissively makes me think that you know it too.
Things are much simpler:
Want a bug free code - do bug free code. Spend time carefully evaluating every line and interaction
Want third-party code and safety - examine that code in the same way
Whatever you do, assume there is a bug in any software you use, so plan and organize accordingly
No amount of magic pills can substitute the above. So yeah, it is a skill issue. Also an issue of kids wining that there are bugs and they don't feel safe, so they want to cling to magic pills instead of dealing with the reality
Strange how your bad faith reply is still here, and with many upvotes, while my reply calling you out appears to be gone.
This is an example of how discussions like this are more appropriate for nostr, where there are no bans / post removals.
You know that bans/removals are documented right? If you don't see your post it's because you didn't post it. You're not being censored, go take your meds
Weak gaslighting attempt but if you could show me where to find it documented I would appreciate that.
If anyone is confused, feel free to ask me for proof I'm telling the truth. If I posted it here, I'm pretty sure I'd be at risk of getting banned for evading the post removal (because the proof would also lead you back to the reply chain that was removed)
Edit - maybe this counts as proof without showing any removed content:
https://piefed.social/post/1458050/comment/8784509#replies
If you click the link, it's blank, yet it has a "parent comment" link that leads to where I was replying
Edit 2 - tried to post an archive link but archive.org didn't seem to work the way I thought?
Is the link I posted above showing what I described for other users?
https://lemmy.zip/modlog?page=1&actionType=All&userId=25498760
Nope, not seeing it there
Yeah I know you don't. It's because your comments aren't being removed
So this link shows a comment for you, not just a blank space? https://piefed.social/post/1458050/comment/8784509#replies
Here's a screenshot of what I'm seeing
Collapsed comment
After opening
Can confirm that post still exists. I just downvoted it. Still exists when I open the link you posted in a browser, too, just collapsed.
There's an ongoing effort to get gcc to compile Rust.^[https://lwn.net/Articles/907405/]
This seems relevant:
https://youtu.be/Fu3laL5VYdM