Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The biggest problem here, though, is that look at Google in web standards: the web is now what Google say it is, IE 6 style. If Googlers don't get their way with the Rust language team, they'll just attack the language team head-on, or bypass them. Google have zero interest in collaboration.


Google employees have actively gotten involved in collaborating within the Rust project rather than bypassing it. Of course, anything can change at any time, but this absolutist statement doesn't correlate with experiences so far.

(Also, these organizations are huge! The web standards folks and the Fuchsia folks are, as far as I know, basically disjoint, so even talking about companies like Google as a monolithic entity is fraught with issues.)


In their own spare time, or as part of their paid work at Google?


I am not 100% sure, but given that the features were directly relevant to their work, I would hope that they were given time to do it on the job.


> If Googlers don't get their way with the Rust language team, they'll just attack the language team head-on, or bypass them.

We work directly with Google folks. This has not been our experience in any way. Likewise for other large companies interested in specific Rust features or improvements.


That's why we're all using dart




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: