mustache_kimono

5 ms·

31.
by mustache_kimono 10mo ago
> Sometimes it's nice to know that something will run and compile reliably far into the future. I'm not sure why you think this is a problem that Rust has? Perhaps you mean something different but the Rust project compiles ava
32.
by mustache_kimono 11mo ago
>> Yes, you can use it everywhere. Is that what you consider a success? > ... yes? Then perhaps you and I define success differently? As I've said in other comments above, C persisting or really standing still is not what I
33.
by mustache_kimono 11mo ago
> Some people isn’t most people and certainly not all people. I never said Rust was the universal language, that is pleasing to all people. I was very careful to frame Rust's success in existential, not absolute or universal, terms
34.
by mustache_kimono 11mo ago
> I'm curious as to which other metric you'd use to define successful? If it actual usage, C still wins. Wait, wait, you can use C everywhere, but if absolute lines of code is the metric, people seem to move away from C as qu
35.
by mustache_kimono 11mo ago
> C will continue to be used because it always has been and always will be available everywhere Yes, you can use it everywhere. Is that what you consider a success?
36.
by mustache_kimono 11mo ago
> You almost certainly have a bunch of devices containing a microcontroller that runs an architecture not targeted by LLVM. This is exactly what I'm saying. Do you think HW drives SW or the other way around? When Rust is in the Li
37.
by mustache_kimono 11mo ago
> Every system under the Sun has a C compiler... My guess is that C will be around long after people will have moved on from Rust to another newfangled alternative. This is still the worst possible argument for C. If C persists in place
38.
by mustache_kimono 11mo ago
> I plan to be writing C for the next decades This is fantastic, if you're still excited about C. However, the question I am asking also has to do with the social relational aspects of programming. Here, significantly, when we are
39.
by mustache_kimono 11mo ago
> COBOL is actively developed and maintained. It's far from being dead. Who said it was dead? I was clear that I thought it was very much undead, like a zombie.
40.
by mustache_kimono 11mo ago
> COBOL has enough business money around to get new tools and ISO standards[0], so it is unlikley to think otherwise regarding C. I don't think you understand my point. I am explicitly saying "C will definitely survive (like C
41.
by mustache_kimono 11mo ago
> Honestly I'd be a bit disappointed if something better came along tomorrow. You'd be disappointed if something 10x better came along tomorrow? I suppose you would you also be disappointed if magically we had economical fusio
42.
by mustache_kimono 11mo ago
> I currently have no reason to believe C won't outlive it, by a lot. My reaction is kind of: "So what?" I really don't care about the relative lives of languages and don't really understand why anyone would. U
43.
by mustache_kimono 11mo ago
Cool. One should perhaps mention some prior art: rustc_codegen_clr is an experimental Rust compiler backend(plugin), which allows you to transpile Rust into .NET assemblies, or C source files.[0] [0]: https://github.com
44.
Tokio (stackless coroutines) vs. May (stackful coroutines) in Rust(crates.io)
4 points by mustache_kimono 11mo ago|1 comments
45.
by mustache_kimono 11mo ago
After investigating may_minihttp[0], which appears, for now, to be the fastest web framework on TechEmpower benchmarks[1], I saw the data below. [0]: https://github.com/Xudong-Huang/may_minihttp [1]: https:/&#x2F
46.
Rust in Production – Jon Seager, VP Engineering for Ubuntu(corrode.dev)
2 points by mustache_kimono 11mo ago|2 comments
47.
by mustache_kimono 11mo ago
> What does it take to rewrite the foundational components of one of the world’s most popular Linux distributions? Ubuntu serves over 12 million daily desktop users alone, and the systems that power it, from sudo to core utilities
48.
by mustache_kimono 11mo ago
> Debian's shipped rustc won't be able to compile Apt since nearly all rust devs are bleeding edge targeters. This is nonsense. Apt devs can target a rustc release and that release can be the same release that ships with Debia
49.
by mustache_kimono 11mo ago
> But it's really wordy and there's a lot of run time overhead. I'm curious: what do the benchmarks say about this?
50.
by mustache_kimono 11mo ago
> This subthread is about claims of STATIC checking of memory safety. A panic is not static checking. Perhaps you should read what you respond to. Oh, I read it. Rust, and for that matter, the person to whom you are replying, above, nev
51.
by mustache_kimono 1y ago
> but rustc-1.63.0 still compiles this program that panics at runtime. An index OOB error? Here, it's important to remember the Rust panic is still memory safe . Perhaps you should read the article, or read up on what undefined be
52.
by mustache_kimono 1y ago
> Also the implied goal of a lot of Rust projects is to replace GPL'ed programs with permissive ones. People really got to stop with crazy nonsense.
53.
by mustache_kimono 1y ago
> Golang doesn't have legions of evangelicals claiming it's a safe language and everything should be written in it. But, to be very clear, Rust has never claimed to prevent deadlocks? See: https://doc.rust-lang.org&#
54.
by mustache_kimono 1y ago
> All the Rust evangelists talk about safety when stuff like this exists? JFC. Deadlocks can happen anywhere? You can replicate this pattern in golang.
55.
by mustache_kimono 1y ago
> To me, Rust rewrites look like "just stop oil" road blocks - the more people suffer, the better. Then blame Canonical? Quit it with the Rust hate.
56.
by mustache_kimono 1y ago
> It's of course not ridiculous. I have the feeling you're arguing against and about something I never said. To clarify, I'll restate: "I believe Linus has even opined that any filesystem which was developed after Lin
57.
by mustache_kimono 1y ago
> Llvm is a different licence (sic) not illegal to examine. FSF considers Apache 2 incompatible with the GPL2 because of its "additional conditions". I happen to agree with you that, at the very least, we haven't fully gra
58.
by mustache_kimono 1y ago
> redox is a pretty cool experimental piece of software that might be the os of the future, why not do it there? Because people want to use Rust where they use C, right now? Whereas yours is a perfectly fine criticism, it ignores that p
59.
by mustache_kimono 1y ago
Check out the disclosure timeline. > 2025-08-11 NVIDIA reiterated the request to postpone disclosure until mid-January 2026. > 2025-08-12 Quarkslab replied that the bugs were first reported in June 18th and mid-January was well past t
60.
A kernel stack use-after-free: Exploiting Nvidia's GPU Linux drivers(blog.quarkslab.com)
172 points by mustache_kimono 1y ago|41 comments

More ›