4 ms·

> Pro: The Fuchsia project has the opportunity to influence the evolution of the language. (RUST) While this may be a Pro for Google, is it also a Pro for the

by scoutt 7y ago

> Pro: The Fuchsia project has the opportunity to influence the evolution of the language. (RUST) While this may be a Pro for Google, is it also a Pro for the users? Does this mean that Google would hold (if not already) a chair in some "foundation" and decide which features goes into the language (and how they will be implemented)? If this is the case, I don't like it very much... That would be a Pro for C, or whatever language out of their reach (as in The Fuchsia project doesn't have the opportunity to influence the evolution of the language).

nicoburns 7y ago
There is no Rust foundation. All of the design and development happens in the open on Github, a public discourse instance, and a few chat programs (zulip, discord, matrix). I believe the Fuchsia project was quite involved in the design of the async-await feature, along with the team behind `tokio` and others.
- scoutt 7y ago
  Sorry, I thought I read somewhere that a foundation might be started eventually. Edit: here: https://news.ycombinator.com/item?id=22008887 https://news.ycombinator.com/item?id=22008887 but I think it's not official.
- rob74 7y ago
  Interesting! Async-await is mentioned as a "pro" for Dart and Rust ("Asynchronous programs can be written using straight-line code"). Seems they really like async-await, and they had more success getting Rust to support it than they had with Go - which might have led to some Google-internal strife?
steveklabnik 7y ago
While the other commentors are correct that there's no Rust foundation, it is true that a member of the Fuchsia team is on the Rust language team, which does decide the direction of the language. It was very much a pro for our users; like any open source project, we need contributors who are willing to help do the work. Fuchsia's experience with async/await was really important to validate that the design worked well; for example, many people think of it as a feature that's useful for web servers only, but Fuchsia demonstrated its validity in other contexts. Beyond semantics, it also helped with syntax; https://github.com/inejge/await-syntax https://github.com/inejge/await-syntax was created during the debate about "prefix await," and was able to show us what a few variants of the syntax would look like in real-world code. > If this is the case, I don't like it very much... That would be a Pro for C, or whatever language out of their reach (as in The Fuchsia project doesn't have the opportunity to influence the evolution of the language). C has a standards process that anyone can get involved in, following ISO rules. Google is a major player in the C++ standards process too.
- scoutt 7y ago
  Thank you for the explanation. I wasn't so wrong after all. Perhaps it was the wording that made me think that way... "To influence". I would rather prefer as you wrote; to collaborate or to contribute. Time will tell...

by scoutt 7y ago

nicoburns 7y ago

There is no Rust foundation. All of the design and development happens in the open on Github, a public discourse instance, and a few chat programs (zulip, discord, matrix). I believe the Fuchsia project was quite involved in the design of the async-await feature, along with the team behind `tokio` and others.

scoutt 7y ago
Sorry, I thought I read somewhere that a foundation might be started eventually. Edit: here: https://news.ycombinator.com/item?id=22008887 https://news.ycombinator.com/item?id=22008887 but I think it's not official.
rob74 7y ago
Interesting! Async-await is mentioned as a "pro" for Dart and Rust ("Asynchronous programs can be written using straight-line code"). Seems they really like async-await, and they had more success getting Rust to support it than they had with Go - which might have led to some Google-internal strife?

steveklabnik 7y ago

While the other commentors are correct that there's no Rust foundation, it is true that a member of the Fuchsia team is on the Rust language team, which does decide the direction of the language. It was very much a pro for our users; like any open source project, we need contributors who are willing to help do the work. Fuchsia's experience with async/await was really important to validate that the design worked well; for example, many people think of it as a feature that's useful for web servers only, but Fuchsia demonstrated its validity in other contexts. Beyond semantics, it also helped with syntax; https://github.com/inejge/await-syntax https://github.com/inejge/await-syntax was created during the debate about "prefix await," and was able to show us what a few variants of the syntax would look like in real-world code. > If this is the case, I don't like it very much... That would be a Pro for C, or whatever language out of their reach (as in The Fuchsia project doesn't have the opportunity to influence the evolution of the language). C has a standards process that anyone can get involved in, following ISO rules. Google is a major player in the C++ standards process too.

scoutt 7y ago
Thank you for the explanation. I wasn't so wrong after all. Perhaps it was the wording that made me think that way... "To influence". I would rather prefer as you wrote; to collaborate or to contribute. Time will tell...