Mozilla began sponsoring the project in 2009 as a part of the ongoing development of an experimental browser engine called Servo, which was officially announced by Mozilla in 2010. Rust grew out of a personal project begun in 2006 by Mozilla Research employee Graydon Hoare. Mozilla Foundation headquarters in Mountain View, California Origins (2006–2012) ![]() Rust has been noted for its growth as a newer language and has been the subject of academic programming languages research. In December 2022, it became the first language other than C and assembly to be supported in the development of the Linux kernel. Since the first stable release in May 2015, Rust has been adopted by companies including Amazon, Discord, Dropbox, Facebook ( Meta), Google ( Alphabet), and Microsoft. Mozilla officially sponsored the project in 2009. Software developer Graydon Hoare created Rust as a personal project while working at Mozilla Research in 2006. ![]() It is popularized for systems programming. Rust borrows ideas from functional programming, including static types, immutability, higher-order functions, and algebraic data types. To simultaneously enforce memory safety and prevent concurrent data races, its "borrow checker" tracks the object lifetime of all references in a program during compilation. It enforces memory safety-ensuring that all references point to valid memory-without requiring the use of a garbage collector or reference counting present in other memory-safe languages. But the foundation's mandate is to support the project, so it'd be a somewhat odd situation if they do find themselves in conflict.Rust is a multi-paradigm, general-purpose programming language that emphasizes performance, type safety, and concurrency. So far, as far as I know, there has not been any serious conflict between them, and it's not entirely clear to me what would happen if there was. They exist in parallel and are mostly-separate entities with mostly-separate areas of responsibility, though there are several people who have roles in both. The project does not take direction from the foundation, nor does the foundation take direction from the project. It's where a decision like "we should put telemetry in the compiler" would be made, not the foundation. The project is in practice responsible for all technical decision-making, in terms of what goes into the language, how the tools and processes work, what content is in the docs, what features to change and when, etc. ![]() They have their own processes and governance system (which they're currently in the process of fairly significantly overhauling after the previous generation of processes. The Rust project which is an informal (not a legal entity) collection of people (some employed by companies, some volunteers) who self-organize into teams (that mostly select their own future membership) who collaborate over the internet, each with their own area of responsibility. There's a fairly broad set of companies involved here: Microsoft, Google, Amazon, Meta, Huawei, etc. It owns the trademarks and domain names, acts as a legal and administrative point of contact when one is needed, and has I think operational and funding responsibility for infrastructure (crates.io, CI, etc.) The foundation has members which are almost all corporate sponsors who donate money (and sometimes people) to further its mandate. The Rust foundation, which is a nonprofit general (delaware) corporation with bylaws, employees, a normal legal existence. Other answers here are imprecise and a bit misleading. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance. Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. Strive to treat others with respect, patience, kindness, and empathy. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity.
0 Comments
Leave a Reply. |