fuck that shit, those rust re-writes are slow as fuck compared to the real thing.

Rust is a decently usable language, and Ubuntu has been a lost cause for over a decade now. Besides, the core utils are actually quite rudimentary, so they really can't fuck it up; moreover, a major player fracturing the ecosystem should hopefully make it even easier to switch to other alternatives like musl or plan9.

So?

Rust is a better language than C

I don't care about tech anymore, I'm not 20 anymore.

so the most bloated distro is getting even slower ?

>>25639716 >the most bloated distro You're thinking of fedora.

who cares about ubuntu lol

All the elite systems programmers are writing in Rust

Wait, GNU core utilities is basically commands right? ls, cd, cp? If so then why, if the current solution has been working just fine for 100 years?

>>25639736 We want, nay, need more cp in our lives.

>>25639682 rip Stallman's life work.

>>25639759 Pretty much shows you how much is grinding tech worth, fuck all.

>>25639759 The GPL is far more important, and I haven't felt a lick of difference after shifting over to other utilities - aside from the occasional script failing to execute properly since it relies on bloated GNUisms.

>>25639711 proofs?

>>25639782 ok tranny

>>25639791 It has a mascot.

>>25639796 Wut?

>>25639791 I think it MIGHT be. I think there are a few Linux distros introducing Rust to their backend (no pun intended lol) but not fully abandoning C.

And the string stuff is obviously not handled very well in C in the first place.

The only thing I'd worry about are the build times.

And gcc. Can Rust even be compiled with GCC yet?

>>25639736 Depends what you mean by "current" and "just fine". They regularly get security vulnerabilities discovered in them, usually something related to memory corruption, which is exactly what Rust is designed to prevent.

I love Rust. My first-born will be called Rusty and it's going to become his first language

>>25639872 >usually something related to memory corruption, which is exactly what Rust is designed to prevent. That's not what rust's memory safety means.

I like Rust, but that seems like a dumb idea. They will probably be slower, if only in startup time (which is a lot of the time if you run "ls" or something), and they in most cases have no remote or even local attack surface.

>>25639855 You can, up to a few years old version. Then it needs to be bootstrapped.

>>25639885 Can you elaborate?

well, what's it gonna be? Slackware, Artix, self harm or just following around lgs at the park and yelling at them in a bad german accent? I'm so 1337, I couldn't even suckstart a BSD.

>>25639892 Nigger I'm talking about whether the Rust compiler has a GCC backend

A working one

>>25639902 Educate yourself

>>25639872 > They regularly get security vulnerabilities discovered in them, Like what? They aren't even SUID root.

>>25639845 you clearly understand nothing about strings

>>25639948 Maybe you were thinking of it, but that's not what you wrote. As to your question, there are projects that transpile Rust to C, but still with some omissions.

>>25639956 There's a good chance I know more about Rust and programming and general than you and than onion taken together. But I'm open to learning new things, that's why I asked. No need to act like an arrogant retard.

>>25639986 Rust is a crutch and proof that you're unsalvageable nocoder.

>>25639993 Rust promises the safety of a high level language at the speed of C without the complexity of JIT runtime. It fails hard on all three points.

>>25639962 https://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-5075/GNU-Coreutils.html

>>25639993 I'll trust my employer's opinion on that over yours, if you don't mind.

>>25640000 meanwhile my C code is as fast as C code and is safe and secure because I thought about it for longer than 5 mins

>>25640008 Maybe you should stop posting and let your employer do it instead.

>>25640001 > Heap overflow > Race condition > Tl;Dr Rust solves neither. Btw, the site blocks Russian IPs, kek.

>>25639902 Rust mostly protects against race conditions - concurrency safety - and dangling pointer errors through its ownership-borrowing system. Rust compilers should also ideally reject invalid memory access and aliasing violations; however, that is one of the reasons for the discrepancy between builds using different versions of the compiler. Runtime array/collection accesses are also checked to some extent, but the program would just terminate itself - anything downstream of it could get fucked if it's improperly set up. Most importantly, if you want to use raw pointers (essential if you need to do anything low level - of particular importance in systems programming) or FFIs with rust, you'll have to wrap them in an unsafe block which bypasses said safety checks. Likewise, integer overflows are not actually rectified during compiler debugging.

>>25640014 >Race condition You can use synchronization primitives.

>>25640001 Most of those have a pretty low score.

>>25640008 You'll be let go this summer once Mozilla loses 80% of funding it gets from Google.