Earlier quoted context omitted.
It has a language definition. Neither Rust not Go have a formal semantics.
What's the equivalent of this[0] in Rust? [0] https://golang.org/ref/spec
[deleted]
Shipping Rust code in Firefox
171–180 of 197 posts
Re: Shipping Rust code in Firefox
#172Even if Servo doesn't pan out as anything more than an experiment (though I'm optimistic that it will), I think Rust will bring real benefits to Firefox by enhancing security of isolated components like this mp4 parser.
Tried rust on my old c2d, feels like alpha level. I thought they'd be closer to a "wow" effect from parallel tree rendering but not in my 4 minutes test. Crashes and memory exhaustion.
Still wishes a safe parallel renderer to emerge so good luck to the team.
Re: Shipping Rust code in Firefox
#173Not in the same league as the mp4 parser shipping to all Firefox users, but GeckoDriver [1], a Mozilla-authored standalone binary for interacting with Firefox via the WebDriver protocol (e.g. using Selenium) is also written in Rust and shipping, possibly to as many as hundreds of users ;) Overall the experience of using Rust for that project has been pretty great; the original requirements for a language were "able t…
I've noticed people coming from high level languages tend to struggle a bit with the borrow checker, did you guys experience this? How did you deal with it?
Re: Shipping Rust code in Firefox
#174Earlier quoted context omitted.
What's the equivalent of this[0] in Rust? [0] https://golang.org/ref/spec
https://doc.rust-lang.org/reference.html , which is accurate, but not always 100% up to date with the latest RFCs. There's also work on a formal, proven specification of the memory model, but that's not done. It'll be a while.
Unlike the Go spec that's prose only. Why is it not accurate? Does the language change that often?
Re: Shipping Rust code in Firefox
#175Super 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/
what's exciting in that?
Re: Shipping Rust code in Firefox
#176Earlier quoted context omitted.
https://doc.rust-lang.org/reference.html , which is accurate, but not always 100% up to date with the latest RFCs. There's also work on a formal, proven specification of the memory model, but that's not done. It'll be a while.
Unlike the Go spec that's prose only. Why is it not accurate? Does the language change that often?
If you're talking about grammar, that's in a different document.
> Why is it not accurate?
I said it _was_ accurate. It's just not neccesarily complete. It's not complete because I'm only one human, and I have more important work to do.
Re: Shipping Rust code in Firefox
#177Earlier quoted context omitted.
> You shouldn't need to test various versions of Rust if you there is a strong backward compatibility policy. Can you specify, in particular, what you think Rust is not doing that it should be doing?
I would like the code developed now to work with all subsequent rust releases until 2.0 so that I can take advantage of improvements to the compiler and std libraries without any additional effort. A small effort may effort may be required if there were security/critical bugs.
Don't use nightly, and your wish is granted!
Re: Shipping Rust code in Firefox
#178Earlier quoted context omitted.
Unlike the Go spec that's prose only. Why is it not accurate? Does the language change that often?
If you're talking about grammar, that's in a different document. > Why is it not accurate? I said it _was_ accurate. It's just not neccesarily complete. It's not complete because I'm only one human, and I have more important work to do.
That's understandable. I've just tried to prove the point that Rust is still a language in flux compared with Go, hopefully making the Rust team aware why some developers hesitate to use Rust on new projects.
Re: Shipping Rust code in Firefox
#179Earlier quoted context omitted.
I don't have a problem with telemetry, provided it is opt-in.
This makes telemetry effectively useless for developers though, unless a big intrusive "Click here to opt in" button is presented during startup. Nobody is going to enable it on their own accord.
I find your comment disturbing because I feel that "Opt-Out" features have become a real problem. The reasons for setting something as opt-out are often self-serving and, even when not, it is still an affront to informed consent (since as we all know that most people will take the defaults).
Re: Shipping Rust code in Firefox
#180Earlier quoted context omitted.
If you're talking about grammar, that's in a different document. > Why is it not accurate? I said it _was_ accurate. It's just not neccesarily complete. It's not complete because I'm only one human, and I have more important work to do.
That's understandable. I've just tried to prove the point that Rust is still a language in flux compared with Go, hopefully making the Rust team aware why some developers hesitate to use Rust on new projects.
I disagree, but I doubt that we're going to agree, so this is where I will step out.