| > Oh no, it seems my one brief post wasn't long and detailed enough to immediately and totally convince some Random Doubter on HN, therefore my 'claims' are 'unsubstantiated.' No, you just didn't cite any actual data, only assertions. Don't come with this excuse of "busy day", you had enough time to create an HN solely for spewing anti-Rust nonsense. Keep in mind, HN is a place for intellectual discussions, not for dumping your pet peeves. If you don't actually have anything actually productive to say, it's preferable to omit yourself before the mods or the flags do that for you. > Nah. It doesn't. Then try to prove it. I already cited a source elsewhere, which you just ad hominem'ed. The burden of proof is now on you. > It's definitely not possible for fluffybucktsnek to just take my word here. I wonder what biases he or she might have. Yeah, what biases does the name "fluffybucketsnek" indicates? "Rust free for me" doesn't sound as impartial in this discussion. It just sounds like you came here for an ideological battle. > Yes, you should just assume that's what must have happened, and then move on, blissfully unaware of how wrong you are. I didn't assume anything. If anything, I kind of wish you did/could prove me wrong. You could, at least, post the code of your fork. Instead, you need us to assume that all your claims, none of which has any sources, are true. All I did was show a different possibility. > Sure it does. There is extra machinery/interfacing for all the extra Rust crap bolted on, and it gets more and more complex over time as they integrate more of the crap. Every FFI introduces some manner of complexity, specially when one language (Rust) is more strict than the other (C++). I don't say C is complex because JNI is a hassle. > Furthermore they vendor the entire Rust compiler, library, etc, all of which has to be compiled first before the browser. That just seems like a Chromium project issue, not a Rust one. It's weird that for issues with C/C++ in Chromium, you blame the project itself, but for Rust, you blame Rust. Just like you don't have to vendor LLVM, you don't have to vendor Cargo nor Rustc along with the project itself. Even for compile times, similar strategies for cutting C++'s work for Rust as well. |