> We're talking about network stacks and network drivers, not web browsers.
Ah yes, the magic web-browser that doesn't do any kind of networking at all.
> Migrating the network stack from the kernel to a user-land process is not going to measurably slow down web browsers, especially on modern systems with IOMMUs and whatnots.
I don't know how you can possibly assert that, it's contradicting computer sciences' current understanding of operating system design as it relates to kernelmode/usermode switching, unless you're doing weird shared-memory things in userspace... which is terrifying.
> That would require rewriting the network stack and network drivers in Rust
Not really, C and Rust can interop just fine, you can have network drivers that are rust but the actual networking stack itself can remain C, if you want.
> but this is not just about memory safety, Rust code can still be vulnerable in many other ways
The post is literally memory safety bugs.
Ah yes, the magic web-browser that doesn't do any kind of networking at all.
> Migrating the network stack from the kernel to a user-land process is not going to measurably slow down web browsers, especially on modern systems with IOMMUs and whatnots.
I don't know how you can possibly assert that, it's contradicting computer sciences' current understanding of operating system design as it relates to kernelmode/usermode switching, unless you're doing weird shared-memory things in userspace... which is terrifying.
> That would require rewriting the network stack and network drivers in Rust
Not really, C and Rust can interop just fine, you can have network drivers that are rust but the actual networking stack itself can remain C, if you want.
> but this is not just about memory safety, Rust code can still be vulnerable in many other ways
The post is literally memory safety bugs.