12 ms·
I believe that's Amazon, Microsoft and Facebook all looking to get involved in core Rust development (I think partially triggered by the Mozilla layoffs). If an
by nicoburns 6y ago
I believe that's Amazon, Microsoft and Facebook all looking to get involved in core Rust development (I think partially triggered by the Mozilla layoffs). If anybody was still harbouring doubts about Rust's future, now is the time to lay them aside.
- johnnujler 6y agoGreat thing but I feel these companies are just too clever for Rust. Rust is a developer’s delight and I don’t want it to become like C++, and I feel the C++ standard got worse especially after these so-called great companies became a part of the standards committee. Or take the example of Web, made worse after the Googles and the Apples of the world got in. So I have mixed feelings about too many clever people doing too many clever things to an awesome language.
- steveklabnik 6y agoThe language team is the sole group of people who decides how the language itself changes over time. Entry into that team is determined by the consensus of the team itself. Anyone can comment on proposals, and of course, a company could hire those individuals, but it's not possible to become a decision maker (or stay one) without the explict consent of the existing set of decision makers. That being said, we (that is, the Rust team broadly, I am not on the language team) do weigh companies' desires fairly heavily, because we want Rust to be used for real, important things by companies. But it's always a balance. Famously, the lang team even resisted some proposals by the Servo team way back in the day, even though most people involved on all sides were Mozilla employees at the time.
- johnnujler 6y agoI am genuinely curious to know more about this. Some of these companies dedicate multiple teams towards an OSS project, which I’ve seen first hand with projects like llvm. So isn’t it possible that the involvement of these companies could actually systemically turn things as most of the people working would be their employees and that the scales could be manipulated easily by these companies(need not be intentional). For example I remember “std::string_view” in c++ being one example which Google pushed and even got into the C++17 standards despite its bad design. Although I might be wrong, but my guess here is that Google had a use for it(which we know it had) and that lot of people on the standards committee being from Google led to a systemic bias. Couldn’t that happen with Rust?
- steveklabnik 6y agoIn very broad strokes, changes to the language work like this: * Anyone may write a proposal * Anyone may comment an open proposals * The people on the Rust team decide to accept, reject, or postpone a proposal. Those people on the team have the power to gate any major decision about the language itself. Some big company could hire 500 Rust developers (let's make it ridiculous on purpose), have them write 1000 proposals for new features, but that doesn't mean that those changes will happen: it requires that team of people to sign off on the decision. That group of people is added to only with the consent of all of the existing members. Additionally, making decisions is a consensus based process, so a single "no" vote will mean the proposal is not accepted. Now, that doesn't mean the process is immune to companies suggesting things. For example, a company could try and hire literally every member of the team. That would be... aggressive. They can use their resources to give more people more time to do the work of making a great proposal, building consensus, and making changes they want to see happen. That is actually an ideal situation, and has been working pretty well historically. (Google employees were key in getting async/await to work out, for example. This is also basically what Mozilla's influence on Rust was for its entire history of working on things.) This is the way I'd personally love to see Amazon (and others) contribute.
- JoshTriplett 6y ago> Rust is a developer’s delight and I don’t want it to become like C++, and I feel the C++ standard got worse especially after these so-called great companies became a part of the standards committee. On the Rust language team, we are extremely mindful of managing complexity, and we typically err on the side of not including a feature (even if it's desired) if it feels like it adds too much complexity or surface area to the language. We've also paid attention to other language design processes and learned from them.
- rodgerd 6y agoThe 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.
- JoshTriplett 6y ago> 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.
- steveklabnik 6y agoGoogle 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.)
- secondcoming 6y agoIn their own spare time, or as part of their paid work at Google?
- estebank 6y agoFrom the article: > Let’s be clear: We understand that we are net beneficiaries of the exceptional work that others have done to make Rust thrive. AWS didn’t start Rust or make it the success that it is today, but we’d like to contribute to its future success.
- steveklabnik 6y agoThey have (including Google) all been involved to various degrees so far; this is about increasing their involvement.
- nicoburns 6y agoSure, but from my perspective (you probably had better insight into these companies involvement than me) there was always a question about how committed companies this large really are when they only have a few projects in the language. Hiring core developers puts all doubts to bed (and also the kind of investment that actually for counts for something).
- steveklabnik 6y agoIt definitely is a significant increase in support, all I'm saying is that it's a difference of intensity, not of kind, that is, it's not going from "no support" to "support" but from "support" to "lots of support." Very happy to see this happening, for all the reasons you cite.
- kortilla 6y agoAs someone who has lived through hype cycles, big companies can pull the rug just as quickly on these investments as they’ve made them. While this does indicate a more serious interest, it’s not nearly the safety net you think. To the contrary, a bunch of FAANG driven contributions tend to make projects focused too much on particular use cases. Go’s clusterfuck of package management is entirely because Google doesn’t do package management.
- steveklabnik 6y ago> a bunch of FAANG driven contributions tend to make projects focused too much on particular use cases This is one of the challenges we have, as a project, in this next phase of its life: make sure that we are helping organizations achieve their goals, while not allowing it to be totally directed by them. Rust governance is set up to be resilient to takeovers by any one organization, but we're now playing with some of the most powerful organizations on the planet. We're glad to have them, but we do have to make sure that we make Rust what we want it to be, and not purely what various large tech companies want it to be. It's a delicate balance.
- SoSoRoCoCo 6y agoFriends of mine that are contract programmers have been ramping on Rust for the past 2-3 years claiming the number of requests for it has been increasing exponentially. I installed it two weeks ago and have been getting a feel for it. It's like if C++, C#, and npm had an offspring. I always hoped Java would make a comeback, but Rust is looking like the real deal.
- johnnycerberus 6y agoApplications of Java and Rust do not overlap. As a big data engineer, Rust does not provide any advantage to me. Good luck rewritting all the big data tools from Java (Elasticsearch, Spark, Kafka, Hadoop, Neo4j, Deeplearning4j, Cassandra, Solr, Arrow, OrientDB) and all the scientific stuff from C++ (Eigen, Tensorflow, PyTorch, Jax, Halide, OpenCV and the multitude of resources for CUDA and OpenCL) and databases (MySQL, MongoDB). If I want to contribute to LLVM or JVM, they are C++, the browsers are all C++. Unreal Engine and Unity (IL2CPP and engine) are all C++. Are you doing microVMs or drivers? Then probably Rust is a good investment (discutable), otherwise, I would wait for better alternatives. I will stick to Java, Scala, Python and C++ for the foreseeable future. EDIT: may the downvotes come from the idealists that hammer down pragmatists, like our opinion doesn't even count
- coddle-hark 6y agoWith this logic there should be no new programming languages ever until there’s a paradigm shift in computing.
- johnnycerberus 6y ago> I always hoped Java would make a comeback, but Rust is looking like the real deal. I was mainly responding to this statement which came across quite aggressive. Java and C++ do not need comebacks and my comment was intended to be a wake-up call to reality. Yes, it is great to learn Rust on the side, but advocating something to be used everywhere is another story.
- 6y ago
- ibraheemdev 6y agoEven Apple is interested [1] [1]: https://www.phoronix.com/scan.php?page=news_item&px=Apple-From-C-To-Rust https://www.phoronix.com/scan.php?page=news_item&px=Apple-Fr...
- weego 6y agoMy questions are about the domains rust ends up getting traction in, not so much whether it will.
- gameswithgo 6y agoAlways hard to know these things. It often doesn't follow what would be rational, but follows various accidents of history. Someone in domain X makes a superb library for it, inspiring ecosystem to grow in that domain, even if the language isn't fundamentally suited for it, etc.
- malinens 6y agoI remember the same story about go while we had microservice craze. Now it is not a sexy language anymore
- dcgudeman 6y agoWhy do you think it has anything to do with Mozilla layoffs?
- vaylian 6y agoBecause some high-profile Rust developers are available for hire again.
- deleted 6y ago[deleted]
- mlindner 6y agoThis meme really needs to die. Mozilla never stopped working on Rust, many of the core developers are still Mozilla employees, and the Firefox team hasn't stopped adding Rust-based components.
- steveklabnik 6y agoWho? This is objectively incorrect. (Well, Firefox adding more Rust is correct, but the rest is not.)