Earlier quoted context omitted.
I would expect the phrase "shipping Rust" to mean that they include the language environment, so that I can write code in Rust with Mozilla.
That doesn't make sense. It is a statically compiled systems-oriented language, not a web-oriented language.
Shipping Rust code in Firefox
21–30 of 197 posts
Re: Shipping Rust code in Firefox
#22Earlier quoted context omitted.
That doesn't make sense. It is a statically compiled systems-oriented language, not a web-oriented language.
The headline is nerdview. http://languagelog.ldc.upenn.edu/nll/?p=26094
Re: Shipping Rust code in Firefox
#23I'm sort of surprised that this is the first time they've used rust for anything in the browser. I thought they developed Rust for this exact purpose?
Re: Shipping Rust code in Firefox
#24AHHH Telemetry! I feel like there is a group of people who freak out to any form of telemetry, I just wanted to highlight them using it to track bugs. It's super beneficial to any form of changes, especially something like switching an entire language for a component.
The restrictions on telemetry on release versions are pretty stringent. It's possible this was measured on release, I'm not aware of the details, but I suspect it wasn't.
Re: Shipping Rust code in Firefox
#25Am I'm reading either the headline or the announcement wrong? As I read it, they are not shipping Rust but a component written in Rust. > For this reason, Ralph Giles and Matthew Gregan built Mozilla’s first Rust > media parser. And I’m happy to report that their code will be the first > Rust component shipping in Firefox.
You did not think, they would replace VanillaJS with Rust, did you? ;)
When WebAssembly is finished, stable, and widespread, I guarantee people will be using end-to-end Rust (among other languages).
Re: Shipping Rust code in Firefox
#26I'm sort of surprised that this is the first time they've used rust for anything in the browser. I thought they developed Rust for this exact purpose?
Re: Shipping Rust code in Firefox
#27Super exciting! I followed Rust at the beginning and I was pleased with the design goals of the language. However, I wasn't thrilled with the pre-1.0 documentation, and even after 1.0 there were breaking changes to the language. Hopefully this is a sign of Rust's maturity. I'll have to look at it again:>) EDIT: s/from/at/
Re: Shipping Rust code in Firefox
#28Does this imply anything regarding rust compiler package for distros? To support the Firefox build, all distros will have to have good rust compiler packages now, right? (I'm sure the status is already not bad, I haven't checked recently..) If it becomes something dependable, infrastructure-wise, like Java, this might mark the beginning of a more serious uptake.
Currently, I believe that this functionality is optional, so distros aren't required to actually ship it just yet.
Re: Shipping Rust code in Firefox
#29Am I'm reading either the headline or the announcement wrong? As I read it, they are not shipping Rust but a component written in Rust. > For this reason, Ralph Giles and Matthew Gregan built Mozilla’s first Rust > media parser. And I’m happy to report that their code will be the first > Rust component shipping in Firefox.
You did not think, they would replace VanillaJS with Rust, did you? ;)
Assuming that they ship another language in addition to Javascript would not be completely out of the question. While it seems that with WebAssembly that is no longer necessary, who knows what Mozilla, in search of future funding, may come up with to open new markets. They also tried creating their own OS for mobile - shipping Rust to further its adoption for whatever to me at the moment inconceivable reason is no less improbable.
So yes, I wasn't sure what to expect from the headline - it said they are "shipping Rust" after all, so something crazy was certainly within realm of possibility.
Re: Shipping Rust code in Firefox
#30I'm curious why rust-url still hasn't been shipped with firefox yet. https://bugzilla.mozilla.org/show_bug.cgi?id=1151899
There are a couple of big pieces of work here: 1) Making the "cargo vendor" story work better. rust-url has a bunch of dependencies, and you have to get them all in-tree. 2) More security review & planning. URL parsing is scary! And we'd want to ship & run it alongside the C++ one to check for places where rust-url is not fully web compatible, but there are major privacy issues in reporting back anything more than "1…