News for hackers. Stuff that matters.
Re:Advancing Memory Safety by hu3 on Tuesday October 15, 2024 @04:19PM (#41852682)
> Part of the magic of learning Rust is realizing that it's a fast compiled language that one doesn't fear to apply to services connected to the open internet. This is so unusual, it may be unique.

Is that sarcasm? If not, thanks for proving my point.

From the top of my head, Go/.NET/Java are fast and safe choices. Also safe in the sense that you won't have a hard time hiring devs that are productive from the get go.

Re:Advancing Memory Safety by timschmidt on Tuesday October 15, 2024 @04:25PM (#41852736)
> often preach replacing GC'd languages with rust in cases where it is not the best fit (mundane web dev for example).

> proving my point.

Was your point misunderstanding that garbage collection != memory safety? Having garbage collection doesn't make a language any better for web dev. Being memory safe does. If you do not understand the difference and needlessly associate the two, you are validating the work put in by the evangelists.

Re:Advancing Memory Safety by hu3 on Tuesday October 15, 2024 @04:32PM (#41852795)
> Was your point misunderstanding that garbage collection != memory safety?

What?! You really think memory safety is binary?

> Having garbage collection doesn't make a language any better for web dev.

It does though. It's more ergonomic than fighting rust compiler and does add safety over manual memory management from the likes of C/C++.

I just want to thank you for demonstrating so clearly how rust evangelists think.

Re:Advancing Memory Safety by timschmidt on Tuesday October 15, 2024 @04:38PM (#41852845)
> What?! You really think memory safety is binary?

Not sure why you'd assume that. The languages you offered are only as memory safe as their runtimes, which are usually implemented in something C flavored, and the compiler for same. Rust identifies memory unsafe areas instead with the unsafe tag. Functionally equivalent but I know which I like more.

> It does though. It's more ergonomic and does adds safety over manual memory management.

This is the misunderstanding. Rust manages to be wonderfully ergonomic without GC. The type system is really the only thing that makes it wordier than C++. And I've written large Rust applications with no manual memory management whatsoever. Occasionally I'll have to wrap something in an Arc Mutex because something needs to run in another thread. One or two variables in a whole application.

Your complaints apply to other languages.

Re:Advancing Memory Safety by hu3 on Tuesday October 15, 2024 @04:55PM (#41853011)
> This is the misunderstanding. Rust manages to be wonderfully ergonomic without GC. The type system is really the only thing that makes it wordier than C++

Thanks for the laugh. Maybe lifetimes/borrow checking syntax got invisible after a while to you. The only explanation.

I'll stop here. Don't have the time nor desire to argue against what seems like passionate opinions.

Re:Advancing Memory Safety by timschmidt on Tuesday October 15, 2024 @04:59PM (#41853056)
> Maybe lifetimes/borrow checking syntax got invisible after a while to you.

I just did a quick scan, in a couple thousand lines of Rust I see two, maybe three lifetime annotations. Nah, not a huge contributor to language verbosity. Most Rust folk seem to work with the compiler's notion of what lifetimes should be, and everything's implicit.

Re:Advancing Memory Safety by vlovich123 on Tuesday October 15, 2024 @09:11PM (#41854705)
Lifetime syntax is only more visible if you try to write high performance code. If you wrap everything in Rc<RefCell> or Arc<Mutex> or Box you’ll not see it show up anywhere but you’ll probably still get a performance profile better than tracing GC because time and time again it’s been shown that reliable tail latencies and peak throughputs are generally harder to achieve with a tracing GC. Where lifetimes start to pop up more is in more complicated situations where you are trying to avoid memory allocations and have even higher performing code.

And op is correct. In terms of memory safety, Java and C# aren’t as safe as you might hope because significant chunks of the runtime are still in C/C++ (not true for Go) and because of JIT miscompilation bugs (also not relevant for go). Of course JIT miscompilation in theory should be the same as a compiler miscompilation, but in practice it turns out to be worse because you have to maintain consistency between the interpreted and all the tiers of JIT at runtime and in practice humans have a hard time doing that which is why V8 constantly has security vulnerabilities in this area. That’s why GraalVM is interesting because it proposes a JIT design where you only have the compiler implemented once.

Re:Advancing Memory Safety by neonsunset on Wednesday October 16, 2024 @12:31AM (#41855619)
Go is not magically exempt from constraints other languages are subject to, no matter how much blind faith is put into this mantra.

Java has different compiler implementations not all of which necessarily go through interpreter stage. .NET CoreCLR does not have one in the first place (there is technically interpreter code in the codebase but it has bitrotted and is unused). JIT or not does not make it inherently more prone to miscompilation bugs. One thing that Go has going for its compiler is it is a massively simpler design. The downside of that, of course, is much worse compiler output that cannot cope with complex code and is inadequate at high-performance scenarios, where the users of Go either have to try to work around this with goasm or might not even have a solution at all, short of rewriting the component in a different language and praying that the FFI call overhead is low enough for the workload in question.

In addition to that, runtime implemented in C/C++ vs Java/C# or other language does not make it inherently safer. It is always a lower-level flavour of the language, where it cannot depend on itself, and with likely numerous relaxations in assurances to stay performant that the authors uphold manually. Even when C or C++ are used - it's usually a limited, focused subset of the language. And it is a bold claim that these runtimes are not extensively tested, fuzzed and otherwise verified against defects before going to production. If you look at bug and CVE history of .NET - pretty much all issues happen in complex "non-core" APIs, often at the unmanaged side provided by operating system rather than .NET itself (the cryptography bits). I can't recall any that are directly or indirectly related to a compiler bugs.

I feel like this reply ignores the wider context, which is plain old web dev, where the use of Rust and the decision fatigue that it carries is likely to be misplaced. Just pick C# or Kotlin.

Re:Advancing Memory Safety by pjmlp on Wednesday October 16, 2024 @02:50AM (#41856271)
Like the Rust compilers partially written in C++.
Re:Advancing Memory Safety by consteval on Wednesday October 16, 2024 @01:30PM (#41861582)
> If you wrap everything in Rc<RefCell> or Arc<Mutex> ... performance profile better than tracing GC

I seriously doubt it. Naively incrementing Ref counters is extremely expensive. Tracing GCs in modern languages are very advanced. The least you could do is try to elide some of the ref increments - but you can't do that in Rust. Also boxing every object is very unpleasant. If you're gonna do that, use a language with reference semantics, like Java or C#

> significant chunks of the runtime are still in C/C++

Means absolutely nothing about the safety of the languages themselves. Just because C# has a runtime written in C++ does not mean that you can now magically compile and run use after frees or whatever.

Re:Advancing Memory Safety by steveklabnik on Wednesday October 16, 2024 @01:46PM (#41861735)
I don’t fundamentally disagree with your points but I do want to point out that in Rust, you have far less recount traffic than in a language that uses reference counting as a GC strategy, because you only increment and decrement on new owners, and not on every access. You can take a regular old &T to the interior of an Rc<T> at any time.
Re:Advancing Memory Safety by consteval on Wednesday October 16, 2024 @06:11PM (#41864345)
I didn't know this, that's pretty cool. Definitely more manual than what Swift is trying to do with RC elision since you have to then deal with runtimes, but also, I'd imagine much more performant due to a finer-grained nature.
Re:Advancing Memory Safety by steveklabnik on Wednesday October 16, 2024 @07:51PM (#41865070)
Yes, and beyond that, you also have the Rc<T> vs Arc<T> split, so if you're not doing multi-threaded, it's not even an atomic increment/decrement.

That said, this is just my intuition here, I've never seen a good benchmark trying to do the comparison, so I don't want to over sell it either. But a lot of times, it's like, "okay I have four threads so I need the refcount to go to four" and then it's just using normal references to actually use the value inside.

Re:Advancing Memory Safety by vlovich123 on Friday October 18, 2024 @08:48PM (#41884754)
I’ve done thorough benchmarking of Rc and Arc.

Rc is cheap to the point of free unless it frees - it’s literally just an addition or subtraction with no data dependency in the path. Your CPU can do > 6 billion of these per second on a 6Ghz CPU (if I recall correctly you could do 3 per clock cycle in a micro benchmark due to out-of-order but at a minimum you should be able to do 1 per cycle).

Arc is quite expensive, particularly on x86 because of its memory model. You can maybe do a few million of them per second. But as you said, you shouldn’t be incrementing ownership once you’ve sent it to a new thread and instead using references directly or using something Rc-like to track the lifetime (i.e. when the current thread’s Rc count hits 0, release your Arc reference).

Re:Advancing Memory Safety by timschmidt on Wednesday October 16, 2024 @02:34PM (#41862230)
> Means absolutely nothing about the safety of the languages themselves. Just because C# has a runtime written in C++ does not mean that you can now magically compile and run use after frees or whatever.

Runtime bugs are potentially exploitable, even from within the language implemented by the runtime. But I don't think anyone's suggested that they'd present as simply as you suggest. Many such bugs have been found in runtimes of many languages.

Compiler bugs can be similarly exploitable, with the caveat that any code eliminated at compile time won't be accessible at runtime, so compiled languages will tend to have a smaller surface area for exploitation in general.

Re:Advancing Memory Safety by vlovich123 on Friday October 18, 2024 @09:01PM (#41884812)
> Means absolutely nothing about the safety of the languages themselves. Just because C# has a runtime written in C++ does not mean that you can now magically compile and run use after frees or whatever.

As security experts like to repeat, it’s a numbers game. You only have to make a mistake once to result in an insecure system. And C++ encourages you to make those mistakes.

Same with JIT - because the compilation happens at runtime, a common attack mechanism is to exploit a particular bug in the JIT implementation so that the generated code violates some assumption and results in unsafe execution. This happens all the time with V8 and a large part of that problem comes from having to implement the language twice (once in the interpreter and once in the JIT and any deviation between the two implementations is an opportunity to exploit a vulnerability). This isn’t something I made up. This is from talking to people who are familiar with this and reading analyses by people who know what they’re talking about.

Compilers btw also have miscompilation bugs all over the place. The reason it’s less of a problem is because the code being executed isn’t “malicious” - it’s your code and you’re not going out of your way to structure code to find bugs in the compiler. This also protects most JIT and why most C# programs don’t have this problem - they’re not loading arbitrary code at runtime to execute. It is a particular problem for V8 though where that’s an expected behavior.

Re:Advancing Memory Safety by surgical_fire on Tuesday October 15, 2024 @04:55PM (#41853008)
Thanks for proving my original point.

I rest my case.

Re:Advancing Memory Safety by timschmidt on Tuesday October 15, 2024 @05:06PM (#41853128)
OK, dude. If you never correct your misconception, you can be annoyed when people attempt to educate you forever X)

No amount of complaining about Rust evangelists will change how they use the language, but you could learn to understand why they're using it the way they are.

Re:Advancing Memory Safety by pjmlp on Wednesday October 16, 2024 @02:50AM (#41856267)
Rust runtime is partially implemented in a C++ toolchain, should we use the same arguement then?
Re:Advancing Memory Safety by timschmidt on Wednesday October 16, 2024 @03:48AM (#41856602)
Yes, Rust does depend on Clang for the lowest level of compilation at the moment. MIR (where the borrow checker lives and most of memory safety is implemented) and HLR are both implemented in Rust.

What argument? Seems more like a misunderstanding to me.

Re:Advancing Memory Safety by pjmlp on Wednesday October 16, 2024 @05:18AM (#41857108)
Using your argument, Rust can't be fully trusted as long as its compilation model and runtime depends on having C++ somewhere.

In fact, that has broken Rust compilation semantics quite a few times already.

Re:Advancing Memory Safety by timschmidt on Wednesday October 16, 2024 @07:13AM (#41857783)
I don't think I've made any contradictory argument. Perhaps someone else did? Or maybe you assumed a binary where I see gradients. I'm quite sure I didn't claim anywhere that any language was perfectly memory safe. With Rust and Cheri we are getting closer, but there is still progress to be made.

I can say that Rust is well architected such that the borrow checker and most of memory safety is implemented in the midlevel intermediate representation, which is implemented using Rust, and the bits of Clang upon which MIR and HLR are built are both well tested by virtue of being used by multiple language frontends, and limited in scope and modularity. It'd be great to see an all-rust replacement though, as bugs in Clang have been found. I believe there are several projects in the works and existing pure-Rust bootstrap compilers sufficient to get the toolchain working.

Re:Advancing Memory Safety by germandiago on Wednesday October 16, 2024 @06:56AM (#41857670)
Rust, like absolutely any language, needs an unsafe base on which to implement safe abstractions.
Re:Advancing Memory Safety by germandiago on Wednesday October 16, 2024 @06:56AM (#41857673)
> Rust manages to be wonderfully ergonomic without GC

Hahahahaha! That's funny.