APT Rust requirement raises questions

Post by enriquto » Tue, Nov 25, 2025, 4:04 PM UTC

superxpro12 wrote: post #123

enriquto wrote: post #96

Earlier quoted context omitted.

> I am thrown back by how... "janky" the syntax is. Well if you come from C++ it's a breath of fresh air! Rust is like a "cleaned-up" C++, that does not carry the historical baggage forced by backwards compatibility. It is well-thought out from the start. The syntax may appear a bit too synthetic; but that's just the first day of use. If you use it for a few days, you'll soon find that it's a great, beautiful languag…

As a c/c++ cmake user, cargo sounds like a utopia in comparison. It still amazes me that c/c++ package management is still spread between about 5 different solutions. IMO, the biggest improvement to C/C++ would be ISO defining a package manager a.la pip or uv or cargo. I'm so tired of writing cmake. just... tired.

Post by rrmm » Tue, Nov 25, 2025, 4:06 PM UTC

honeycrispy wrote: post #80

epolanski wrote: post #11

Earlier quoted context omitted.

The problem is that rust is being shoved in pointless places with a rewrite-everything-in-rust mentality. There's lunatics that want to replace basic Unix tools like sudo, etc, that are battle tested since ages which has been a mess of bugs till now. Instead Rust should find it's niches beyond rewriting what works, but tackling what doesn't.

Calling it pointless comes across as jaded. It's not pointless. Supporting Rust attracts contributors, and those contributors are much less likely to introduce vulnerabilities in Rust when contributing vs alternatives.

Post by creata » Tue, Nov 25, 2025, 4:08 PM UTC

dv35z wrote: post #31

Every time I consider learning Rust, I am thrown back by how... "janky" the syntax is. It seems to me that we ought to have a system-level language which builds upon the learnings of the past 20+ years. Can someone help me understand this? Why are we pushing forward with a language that has a Perl-esque unreadability...? Comparison: I often program in Python (and teach it) - and while it has its own syntax warts & fr…

Post by nullpoint420 » Tue, Nov 25, 2025, 4:09 PM UTC

simonask wrote: post #82

simonw wrote: post #71

Earlier quoted context omitted.

trait Handler { fn handle (&self, input: &'a str) -> Result ; } fn process_handler ( handler: Box , input: &'a str, ) -> Result { handler.handle(input) }

> > really extreme use cases with lots of lifetime annotations and generic bounds You choose as your example a pretty advanced use case.

Post by juliangmp » Tue, Nov 25, 2025, 4:11 PM UTC

kataklasm wrote: post #127

tcfhgj wrote: post #113

Earlier quoted context omitted.

I am coming from C++ and think Cargo is a blessing. I like that I can just add a dependency and be done instead of having to deal with dependencies which require downloading stuff from the internet and making them discoverable for the project specific tool chain - which works differently on every operating system. Same goes for compiling other projects.

But that is the kind of convenience and ease of use that brings us another npm malware incident every other month at this point.