Is it just me, or does that seem … abrupt?
Rust adds another layer of trusting the compiler isn’t backdoored. All UNIX/Linux systems use the gcc toolchain, so having it written in C would mean less dependencies for the OS.
- paraphrased from someone who seemed to know more about this stuff in this unrelated discussion yesterday
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
It’s not a “magic pill”, it’s another tool. We’re not saying that it will magically fix everything, it will just make certain types of errors less probable.
If you want bug-free code, will you (A) use a tool that makes it easier, or (B) use the same tool as before?
“Skill issue” is not an answer.
Wrong reasoning, friend:
Maybe C++ has rotted their brain to the point they can’t “get” the borrow checker.
Yeah, sure. Borrow checker fixes all. This is exactly the idiot attitude I am addressing.
And if I want a bug-free code, I will use same tool as ever: my brain
-
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.
Still gonna use Debian.
This shoehorning of Rust feels more artificial than Wayland’s. 🤔
Uhm, what?
Wayland has been in the works for more than a decade. Granted, there’s some people having issues with it, with propietary hardware (nVidia) and not-so-common setups like two monitors, but it happens that they are the most noisy. For the rest of us it’s been great, stable, and feels snappier than X.
If you want to talk about shoehorning stuff into Debian, talk about systemd.
not-so-common setups like two monitors
wat.jpg
deleted by creator
