Implications of Rewriting a Browser Component in Rust

Re:Implications of Rewriting a Browser Component in Rust by coldtea on Thursday February 28, 2019 @12:55PM (#19273358)

>Yeah I keep hearing / reading about rust, even seen some demos but the demos all end with "oh no I'm not using this for anything". Still cool but ... want to see someone doing something in production / get their thoughts on that.

Huh? Besides Mozilla itself using it in the browser in several backends, there are tons of places where its used in production (and several articles on HN on the topic).

Where do you see all those demos who say "I'm not using this for anything"?

I've seen articles on Mozilla using Rust, Dropbox using Rust, MS using Rust (rustgrep used in VSC but also something in Azure IIRC), Google using Rust (Google Fuchsia), Facebook using Rust (Mononoke, etc), and so on.

[ Parent | on HN ]

Re:Implications of Rewriting a Browser Component in Rust by M2Ys4U on Thursday February 28, 2019 @10:11PM (#19277637)

Amazon is using Rust - Firecracker powers Lambda and Fargate: https://aws.amazon.com/blogs/aws/firecracker-lightweight-vir...

[ Parent | on HN ]

Re:Implications of Rewriting a Browser Component in Rust by capdeck on Thursday February 28, 2019 @04:14PM (#19275270)

NPM is using Rust on the backend

[ Parent | on HN ]

Re:Implications of Rewriting a Browser Component in Rust by eridius on Thursday February 28, 2019 @05:35PM (#19276003)

I believe Discord is using Rust for their games store.

[ Parent | on HN ]

Re:Implications of Rewriting a Browser Component in Rust by pjmlp on Friday March 01, 2019 @02:33AM (#19278613)

MS security devision is also proposing a trio of C#, Rust and constrained C++ (meaning no Cisms) for their software going forward.

[ Parent | on HN ]