12 ms·
Laying the foundation for Rust’s future
- cs702 6y agoTL;DR: 's/Mozilla Foundation/Rust Foundation/g' The creation of an independent non-profit foundation that will legally own and control all digital and physical property associated with the Rust language (from the Rust name itself to domains like crates.io) is a great development for the language. IMHO, this was overdue: Rust's impact and influence today is global, and extends well beyond the confines of Mozilla. Many businesses and organizations building mission-critical applications with Rust will now be able to support and influence development of the language more directly through the new foundation. Long term, I have an inkling that it will lead to greater/broader adoption of Rust.
- mwill 6y agoI have to be honest, I thought this was already the case.
- Manishearth 6y agoWhen it comes to the Rust project: it was already well outside the confines of Mozilla, with an independent leadership team, and with a lot of the infrastructure being run by other companies (Github/Microsoft for CI, Amazon for storage, etc) The main stuff that was left over was the trademarks, domains, and some infrastructure.
- steveklabnik 6y agoYeah, it's just really hard to get things right. And time spent managing a foundation's business takes time away from managing the project itself, at least in the beginning, where there is significant overlap. Basically, bootstrapping is always a hard problem :)
- dathinab 6y agoBehind the scene work for this already started last year (or even earlier?). The recent events are if anything only an aclerator for this.
- manquer 6y agoIt is good news that rust is settling up a independent foundation. If other shelved or high risk Mozilla projects such as MDN , servo , thunderbird setup similarly it would enable us to directly contribute to the projects instead of the foundation or not at all. The only project the corporation would never let go is Firefox as it their revenue source , however other projects could perhaps be salvaged
- 0xcoffee 6y agoI agree it would be best if FF was it's own foundation. I would like to hear some arguments from Mozilla about this. It seems an idea that only has upsides to me. I get the feeling Mozilla is kind-of hijacking the donations people think are going towards Firefox.
- dleslie 6y agoSome folks believe very strongly in the advocacy that Mozilla undertakes, and believe that separating the software efforts from the advocacy would diminish the funding for advocacy. Which is probably true; Google is unlikely to spend half a billion a year on Mozilla's advocacy efforts.
- whyever 6y ago> Google is unlikely to spend half a billion a year on Mozilla's advocacy efforts. AFAIK, Google's money goes to the Mozilla Corporation, while the donations go to the Mozilla Foundation. So the advocacy is already separated, isn't it?
- dleslie 6y ago2% of annual net-revenues from MozCorp go to the Foundation; and Google's deal is with the Foundation, but I'm iffy on how much makes it straight into MozCorp. https://en.wikipedia.org/wiki/Mozilla_Foundation#Financing https://en.wikipedia.org/wiki/Mozilla_Foundation#Financing
- lifthrasiir 6y ago> This foundation’s first task will be something Rust is already great at: taking ownership. Oh, I honestly never expected that line. Good job, and good luck to the foundation efforts.
- 1f60c 6y agoThat line made me LOL.
- agumonkey 6y agofast languages steal, safe language borrow ?
- nine_k 6y agoThis implies that safe languages are not fast; this is not necessarily so, and in the case of Rust, manifestly not so. Maybe "loose languages steal".
- danfo 6y agoYeah this one made me smile.
- tus88 6y agoWell it better have a commensurate committee process that is as convoluted and bureaucratic as developing anything non-trivial in Rust is.
- TypeCaste 6y agoThis is great news for Rust! Maybe I missed it in the post, but what is the name of the foundation? Rust Foundation?
- pietroalbini 6y agoThis is still a open question! We made no decision on the name yet.
- mucinoab 6y ago"Iron" seems like a fun/nice option.
- Jarwain 6y agoCould call it Oxygen, or Oxidize, or something along those lines
- Argorak 6y agoOxidize is taken by a Rust conference :). oxidizeconf.com
- rswail 6y agoThe Fe foundation, or "FeFo" in short.
- richardwhiuk 6y agoPersonally I think anything beyond "Rust Foundation" or "Rust Language Foundation" risks merely confusion over purpose.
- noisy_boy 6y agoI agree. Something like Rust Language Foundation has both the clarity and gravity that it deserves. We will always have crates and components for fun names.
- rectang 6y ago
- rvz 6y ago> Mozilla and the Rust Core Team are happy to announce plans to create a Rust foundation. Our goal is to have the first iteration of the foundation up and running by the end of the year. Good idea. I can definately see this working out for Rust. > The various trademarks and domain names associated with Rust, Cargo, and crates.io will move into the foundation, which will also take financial responsibility for the costs they incur. Very important folks. This direction looks very interesting. We'll see what happens.
- oconnor663 6y agoWhat other programming languages have established foundations like this? The other one I know of is the Python Software Foundation.
- gardaani 6y agoZig: https://ziglang.org/zsf/ https://ziglang.org/zsf/
- arusahni 6y agoBased on an inartful Googling, here are some additional ones: * D [1] * F# [2] * Perl [3] I'm sure there are more. 1: https://dlang.org/foundation/about.html https://dlang.org/foundation/about.html 2: https://fsharp.org/ https://fsharp.org/ 3: https://www.perlfoundation.org/ https://www.perlfoundation.org/
- steveklabnik 6y ago"like this" is complicated, because different foundations do different things, but, beyond the Python Software Foundation, there is: * The OpenJS Foundation (Node) * Ruby Central is similar but also different * Parrot (for Perl 6...) had a foundation, not clear on what the project is like now though * https://www.perlfoundation.org/ https://www.perlfoundation.org/ And of course, many many foundations that support open source projects that aren't programming languages.
- RabbitmqGuy 6y agoZig also debuted their foundation a few weeks ago; https://ziglang.org/zsf/ https://ziglang.org/zsf/
- aloisdg 6y agoThe first coming to my mind is the .NETfoundation https://dotnetfoundation.org/ https://dotnetfoundation.org/ baked by Microsoft but more and more community driven
- deleted 6y ago[deleted]
- adamnemecek 6y agoYou should setup donations ASAP. I think that now is a good time to do that since a lot of Rust users are somewhat upset by the recent events and would be willing to help out.
- steveklabnik 6y agoHey Adam! Thanks for that comment the other day :) We need the foundation to exist before we can accept donations, unfortunately. And that takes time.
- emosenkis 6y agoOf course that's true for accepting donations, but what about contributions that aren't treated as donations? Or could another foundation receive donations and hold them in trust until the new foundation is able to receive them? Is the new foundation actually expected to be in immediate need of funds such that this would be worth considering?
- steveklabnik 6y agoThere are setups like this, but it all involves paperwork and legal stuff and time. :) We do not immediately need funds, so it is probably a distraction, yes.
- adsjhdashkj 6y agoEspecially as many people, like myself, are questioning donating to Mozilla at all after these recent changes. While i like FFs existence, Mozilla is being disassociated with FF - to me at least.
- ajross 6y agoDoes it seem tone-deaf to anyone else that this blog post is clearly written from the perspective of and to be interpreted as the opinion of the Mozilla project leadership and not the "Rust Project"? I mean, if there's any time where you want to be clear about the distinction it would be now, right? What people who really care about Rust need to know now is that it will prosper outside the control of its corporate backer. Telling us the Mozilla still supports Rust (at a time where it's by definition true that it is reducing its support) is communication that should come from Mozilla, not rust-lang.org.
- GoblinSlayer 6y agoWell, Mozilla is Rust's killer feature.
- eminence32 6y ago> Does it seem tone-deaf to anyone else that this blog post is clearly written from the perspective of and to be interpreted as the opinion of the Mozilla project leadership and not the "Rust Project"? I didn't get that impression while reading this blog post. Is there something in particular that gave you this impression? (Mozilla doesn't really have any leadership role in Rust, as I understand it)
- steveklabnik 6y ago> is clearly written from the perspective of and to be interpreted as the opinion of the Mozilla project leadership Could you say a bit more about what makes you read it like this? It is from the Core Team, one of which is employed by Mozilla to work on Rust, and one of which was laid off and contributed to Rust in their spare time. (out of 9 people) Mozilla is an important part of this transition story, which is why we included the stuff about them; there's no way to ignore the intellectual property owner when discussing how that property will be transferred to another entity.
- jonesetc 6y agoWhile I don't share the sentiment of the OP, I would guess lines like this may be the key for them: >Mozilla and the Rust Core Team are happy to announce plans to create a Rust foundation. Our goal is to have the first iteration of the foundation up and running by the end of the year. I read this as "Mozilla is currently still largely in control. This is the moment where they will cede to the new, more independent, foundation." But the fact that it follows "Mozilla and the Rust Core Team" with "our" may taint the rest of the use of "our" throughout the post for others.
- pjmlp 6y agoGood news. All the best for Rust going forward.
- bzb4 6y agoWhat I want to see is a Firefox foundation.
- awild 6y agoI'm not clear on the specifics, but will Mozilla continue to finance active development in rust? The announcement is ambivalent on this, could they actually be trying to remove another cost factor from their portfolio?
- pietroalbini 6y agoMozilla has had to reduce its investment in Rust significantly, but it’s not abandoning Rust. Mozilla has committed to financial and logistical support while we get the foundation up and running, and we expect they will become a sponsor once that is an option.
- pcwalton 6y agoThere are still Rust team members working at Mozilla, so yes.
- giovannibajo1 6y agoIt’s not clear whether they will continue to be assigned to Rust, though. At least, I didn’t find this explicitly confirmed anywhere. If anything, I’d love to know how many Mozilla employees were working on Rust full-time as their paid job before the layoffs, and then after. I can’t find these numbers cited anywhere. Pietro’s sibling answer seems to be that Mozilla will transition to be a sponsor — I’d love to know whether this means they will keep investing development time (and how much).
- M2Ys4U 6y agoOne important question not touched on my the blog post: Where will the Foundation be located? Will is be US-based like Mozilla, or will it be somewhere else, like Europe? A couple of foundations have moved away from the US in recent years, for example the Eclipse Foundation (Belgium) and the RISC-V Foundation (Switzerland). It seems foundational (if you'd forgive the pun) to know under what laws the foundation will operate, and who (if anybody) will be excluded from taking part in the project because of sanctions regimes.
- steveklabnik 6y agoWe have not made that decision yet.
- dragonsh 6y agoHopefully not in USA, will like it to be in Europe given its stance on software patents and privacy.
- k__ 6y agoYes, the US doesn't seem safe.
- dcgudeman 6y agoDoesn’t seem safe? Honestly, what do you think will happen to this organization if it were to be headquartered in the US?
- mcintyre1994 6y agoTongue in cheek - kind of? If a country can try banning the export of cryptography, why not try banning the export of programming languages to say China? After all US companies make lots of important ones!
- qppo 6y agoDisclaimer: I'm American. Our government has repeatedly made it policy to block access to software of domestic origin through export controls [0] [1] Historically I'd argue most nations could trust the US government only to wield economic sanctions against our adversaries, but the current administration has made all nations our adversary. I can see a real possibility of the current administration enacting export controls on the European Union for a perceived slight against the President, and Congress will not stop him. For example, if crates.io is an American-based software service, there is a real possibility that the US could ban the owners from allowing access from EU IPs. Granted, the same is true of GitHub, npm, freaking google... but the tl;dr is that I don't think you can trust us today or tomorrow. I don't trust my government, why should you? [0] https://techcrunch.com/2019/07/29/github-ban-sanctioned-countries https://techcrunch.com/2019/07/29/github-ban-sanctioned-coun... [1] https://www.eff.org/deeplinks/2019/08/us-export-controls-and-published-encryption-source-code-explained https://www.eff.org/deeplinks/2019/08/us-export-controls-and...
- ww520 6y agoThis is actually good news. Rust was in the Mozilla incubator for the longest time. Moving out signals it’s mature enough to stand on it own. Mozilla has done a great job in incubating Rust. Now is the time for Rust to fly on its own wings.
- Manishearth 6y agoI want to clarify: The Rust project has been largely "outside" of the Mozilla incubator for quite a while already; with most of the governance being non-Mozilla individuals. The main things Mozilla provided was infrastructure (a lot of which has moved out in the past year), trademark ownership, and paying some people to work on Rust full-time (which many companies do now). Make no mistake, Mozilla has contributed a lot to the Rust project, but the particular stage of maturity you mention was achieved some years ago :)
- da39a3ee 6y agoWhy are Mozilla clearly so closely involved in the announcement of the creation of a foundation? To be honest it does come across that the desire to state that there is distance between Rust and Mozilla somewhat exceeds the actual distance. Certainly it's understandable, based on this language, that GP understood the moment of separation to be more "now" than "several years ago". > Mozilla and the Rust Core Team are happy to announce plans to create a Rust foundation. Our goal is to have the first iteration of the foundation up and running by the end of the year. (Later changed to > the Rust Core Team and Mozilla are happy to announce plans to create a Rust foundation. The Rust Core Team's goal is to have the first iteration of the foundation up and running by the end of the year. )
- deleted 6y ago[deleted]
- Manishearth 6y agoThe text was changed due to feedback provided elsewhere in this HN page. The blog post was drafted by the core and foundation team, however we did get sign-off from Mozilla on it. Mozilla currently owns the trademarks that the Rust foundation plans to take ownership of, so they have to be involved to some extent. They have agreed to transfer it as mentioned in the blog post, and are going to work with us to make that happen. The Rust project as an open source project with open governance has been pretty independent of Mozilla for quite a while now. However, Mozilla did provide some crucial services including trademark ownership, which is _extremely_ relevant to the discussion of forming a foundation. Trademark ownership and is rarely impactful to the day-to-day workings of the Rust project, which is why I consider these irrelevant to whether or not Rust is still being "incubated" by Mozilla.
- mrweasel 6y agoThis might just be me being weird, but does anyone else feel like the makes Rust even more interesting. Best of luck to the Rust foundation.
- jetti 6y agoI don't understand what this actually means or any implications of this other than the IP being transferred which would prevent Mozilla from shutting it down and the community having to fork under a new name and to also allow monetary donations. Is the long term goal for a foundation like this to eventually hire full time devs?
- steveklabnik 6y agoThe trademarks being transferred is the primary implication right now. Part of why we've been discussing this so long and not made moves yet is that there are a lot of things that a foundation could do, like hiring devs. But we're unsure what we would want to commit to it doing. Hiring devs has some big advantages, but also a lot of disadvantages too. For now, we're focusing purely on the trademark ownership part, as a sort of MVP.
- UncleEntity 6y ago> Hiring devs has some big advantages, but also a lot of disadvantages too. The Blender Foundation has been employing devs for, like, forever -- they're (usually) the ones who fix all the little things since everyone else wants to work on 'more cowbell'. Maybe shoot Ton Roosendaal a friendly email or something as he has years of experience in this matter?
- steveklabnik 6y agoThe project group is aware of the Blender foundation, but I appreciate the tip!
- Matthias247 6y ago> Hiring devs has some big advantages, but also a lot of disadvantages too I'm curious on what or those from your point of few. From the disadvantage point I can see: It won't be easy to figure out what they should work on. I think if you have a foundation which has sponsors that pay for dev-time, those might also want to see the issues and features prioritized that they are interested in. However devs might have different desires on what they want to work on. That's kind of true for every environment, but I guess it might even be more true in an environment like Rust which attracts a high amount of smart, creative and passionate people. Now this can obviously be dealt with via project management. But I think that still might not exactly be what some of the Rust contributors hoped to get out of a foundation (getting paid for working on stuff they like).
- nickx720 6y agoGreat news :)
- mseepgood 6y ago> in the middle of a global pandemic "global pandemic" is a pleonasm.
- mcintyre1994 6y agoNever heard that word before, nice!
- colesantiago 6y agoand your point is?
- AlexanderDhoore 6y ago> pandemic : an outbreak of a disease that occurs over a wide geographic area and affects an exceptionally high proportion of the population https://www.merriam-webster.com/dictionary/pandemic https://www.merriam-webster.com/dictionary/pandemic So a pandemic can be "local" to a country or continent. Doesn't have to be global.
- mlindner 6y agoThe "pan-" in pandemic is more a sense of "all" but what "all" is over can be all of a country or all of the world. https://www.merriam-webster.com/dictionary/pandemic https://www.merriam-webster.com/dictionary/pandemic https://en.wiktionary.org/wiki/pan-#English https://en.wiktionary.org/wiki/pan-#English
- wongarsu 6y agoIn these challenging times we all like our clichés.
- blargmaster33 6y agoMore SJW?
- david_draco 6y agoMozilla created something extremely valuable and long-lasting here.
- rectang 6y agoThe biggest question I have is whether or not this new foundation will be a 501(c)(3) charity (or European analogue), versus a 501(c)(6) "business league". The big distinction between the two of them is that donations to a 501(c)(3) charity are tax deductible and therefore may not be used to unduly advantage any commercial entity, while donations to a 501(c)(6) are not tax deductible and thus are unrestricted. If it's a 501(c)(6), then the foundation will serve its biggest donors first and foremost. In theory, it may also serve the public good — but only to the extent that it is in the interest of those donors.
- deleted 6y ago[deleted]
- mikeyouse 6y agoA reasonable BOD can ameliorate any of the downsides with a (C)(6) quite easily, and while the perception may linger, it's entirely possible and likely that the Foundation will serve the Rust community regardless of whatever legal structure they choose. There are plenty of reasons to avoid (C)(3)s as well if you do want to fund the project with corporate dollars since those contributions are usually routed through an organization's philanthropic arm and usually can't be approved by business unit owners. (C)(3)s also have more stringent reporting requirements which can be a nice 'check' on any abuses but usually result in a lot more overhead.
- rectang 6y agoI've served on a non-profit board (the Apache Software Foundation, which is a 501(c)(3)), and I don't believe that counting on the composition of the board to maintain independence would be reliable. Board members come and go. If you care about independence, it should be baked into the corporate structure. It is true that it is more difficult to get funds for a 501(c)(3) than a 501(c)(6). That forces the organization to operate lean and constrains possible initiatives (e.g. funding development), but also serves as a buffer against influence. Paradoxically, a maximally independent organization may serve the interests of the long tail of potential corporate donors, because they don't have to worry that the biggest player in their space will capture it via pay-to-play. (For those not up on the acronym, BOD stands for Board Of Directors in this context.)
- whynotwhynot 6y agoI tried getting into Rust, but found its ownership model to be a bit too cumbersome (for me, maybe not for you.) I'm playing with various PLs designed for safe concurrency, including this one called Pony: https://news.ycombinator.com/item?id=24201754 https://news.ycombinator.com/item?id=24201754 Hopefully not off topic, as both Rust and Pony share a similar agenda.
- hu3 6y agoInteresting. How mature is Pony? Is it used in production?
- whynotwhynot 6y agoYes From 2017, https://blog.wallaroolabs.com/2017/10/why-we-used-pony-to-write-wallaroo/ https://blog.wallaroolabs.com/2017/10/why-we-used-pony-to-wr...
- Ar-Curunir 6y agoIt is off-topic, given that the article is not about the merits of Rust, but rather the Rust foundation
- ncmncm 6y agoThis post will trouble many Rust fans, tempting them to "downvote it to oblivion", because it voices uncomfortable truths. This is a critical time in Rust's history, and choices made now will determine whether Rust succeeds and achieves a long-lasting and influential presence, or fades into fond obscurity like the overwhelming majority of its kin. Make no mistake, the latter course remains very, very possible. At their peaks, no one would have believed this fate would take Common Lisp, Ada, Oberon or Pascal. Each had a vigorous ecosystem and numerous devoted users and implementers. Each still has devotees in its obscurity, but each's present obscurity is undeniable. These truths must be voiced, and acted on, if Rust is not to share the fate of those once equally-vigorous languages. The first uncomfortable truth is that the numbers matter. It is not enough, for a language to succeed, to gain new users, trying out the language, at a satisfying rate. They must also remain users, and must find, before they give up, that early difficulties adjusting fade. They must find the language better, on all the axes that really matter, for the problems they face, than what they have used before. Hard as it may be for it fans to believe, this is not the universal experience. Rust is stronger on some axes than the languages people come to it from, and weaker on others. It must become strong on all. The borrow checker, as it is implemented, ultimately turns away too many new users before they achieve proficiency, and burdens exploratory designs when they are least ready to carry it. The slowness of builds is an enduring impediment to production use that will not continue to be excused. The NPM-like ease of falling into unwise dependency on abandoned library components, and the permanence of unfairly-claimed names in the repository, are traps that lead to troubling experiences. Scrupulous users will identify other problems. To achieve maturity is not the norm, for any language. It is, it must be repeated, a game of numbers. A large-enough number of people must be motivated to try it. A large-enough subset of those must find enough to like to motivate them to continue learning. Enough of them must stay long enough to learn enough to do their regular work in the language. And, enough of those still on board must find a place where they can actually do their work in the language. If any of these numbers is not large enough, for long enough, the language will unavoidably fade into obscurity, deserved or not. As popular as Rust already is in some pockets of the wide internet, these numbers are not now large enough for Rust to endure and not fade. The window during which its newness and trendiness are enough, on their own, to motivate people to try it is rapidly closing. While nothing can guarantee success, many things can guarantee failure. One of the latter would be not to change what keeps the numbers down. Needed changes will be unpopular with self-selected early adopters who overcame difficulties and have little contact with those who did not, and left; but change is necessary. The first and most uncomfortable change needed is to make the borrow checker less draconian. Allow beginners to know how many violations they have, yet run. A running and useful program motivates improvement at every level, ultimately including rigor. Dead code benefits no one, howsoever clean it is. Beginners exploring the language need early, even if partial, successes. Everyone exploring the design of a new program has far more urgent concerns than borrow rigor. Those can always be returned to, in time, and will be if they remain visible. Allow libraries with violations to be used, and even to be shared, unguarded by "unsafe" blocks; still noting, in each build, how many violations remain. Rust's reason for being invented was to displace unsafe languages from use where they are most harmful, most particularly C. In this it is, however resolutely, failing. The C users who remain have seen many, many languages rise to popularity and fade away, and have resisted all temptation. They are self-selected to continue resisting temptation. Most remaining C users love it for its faults. They are proud to overcome C's faults, individually, without help. Most former C users who might have jumped already did. Many jumped to C++. Coding C++98 is enough like coding C that the merits of Rust, particularly its modernity and its initial simplicity, had appeal. But Rust has become complicated, and C++ has evolved, through C++11, C++14, C++17, now C++20, soon 23, and 26. Coding C++20 is little like coding C++98; 98's temptations to unsafety do not appeal. Furthermore, C++ is and will remain a much stronger language than Rust for capturing semantics in libraries. Moving to Rust means a dizzying step down in expressive power, both in ability to capture semantics in libraries and to use the uniquely powerful libraries it has enabled. While such power is needed in a minority of applications, it is needed badly there. C++ is not being displaced by Rust. New Rust users are coming, predominantly, from other languages instead, notably Java and Go, and scripting languages. Rust is an overwhelmingly better design than the first two, and runs overwhelmingly faster than the others. But its safety, when borrow-clean, does not distinguish it from them. The appeal of safety is not what wins the users it gains today. Rust wins users from these languages by being a better experience. The borrow checker is just tolerated, in exchange for the language's modern and substantially more powerful design, including its Drop trait that enables programmed control of resources, its default const and default pass-by-move semantics, and the careful, comprehensive and coherent design of its built-in and core library types. If Rust succeeds and does not fade, it will be by playing to these strengths among current users of these other languages, but moreso by resolving its weaknesses. The painfully slow compiler can and must be replaced, if it cannot be fixed. The library ecosystem must be made a strength, not a cause of weakness and fragile dependency. And the borrow checker must become an aid to rigor, not a gauntlet for beginners to suffer and, too often, fall to. Rust's future will be assured only when more complain of its flaws than boast of its successes.
- GuB-42 6y agoIt is nice that Rust is getting an independent foundation but I hope it will not be too independent. My idea of programming languages is that they are better when they are designed with their use case. And in the case of Rust, it is to make a web browser engine. I don't know what the current situation is with Servo but I think that it would be a good thing to keep a privileged relationship between the Servo team (or what is left of it) and the Rust foundation. Rust is not for every project, in fact it is terrible for many projects, but if your project has the same needs as for a web browser engine, then it is great. By making the foundation too independent, we may end up with a monster (no need for another C++), a useless "jack of all trades, master of none", or simply lacking features that are essential for making a good web browser because it is not good enough for some committee.
- Someone1234 6y agoIt may be a controversial opinion, but I actually agree. Languages need a strong direction, with specific goals in mind. Otherwise, they just wind up being a little bit of everything and not really great at anything (or wind up with a dozen duplicate implementations of the same idea). I don't think Rust should be limited to just a browser engine language though, multiple companies are already looking at it to 1:1 replace some C++ for its security improvements without sacrificing significant runtime performance.
- steveklabnik 6y agoThere is an implicit assumption in your post that a foundation would have governance over the language itself. The Rust project is already organized with a pretty de-centralized team structure; the language team gets to decide what's in the language, and nobody else. I'm on the core team and I don't get to make these calls! So, I don't think you have much to worry about there. :)
- charlieflowers 6y agoI really think this is the key question: > If anything, I’d love to know how many Mozilla employees were working on Rust full-time as their paid job before the layoffs, and then after. I can’t find these numbers cited anywhere.
- steveklabnik 6y ago4 total, one not laid off, two laid off, unsure about the final person.
- charlieflowers 6y agoAny idea or guesstimate how many other people are paid (by employers other than Mozilla) to work full time on Rust?
- steveklabnik 6y agoI don’t know, it’s hard to keep track of ~200 people.
- Animats 6y agoWait, Mozilla already is a foundation. The foundation owns the Mozilla Corporation and has some other activities.
- steveklabnik 6y agoThat is true. I'm not sure how it's relevant though. If we're trying to be independent, the status of Mozilla is not really of note, no? (And all Rust stuff is under the corporation, not foundation.)
- alpineidyll3 6y agoHey any rust ppl laid off and looking for work. Feel free to reach out. I'm head of data at a small HF.
- majewsky 6y agoI'm probably just fantasizing, but it would be great the Rust Foundation took over Servo and they built it into its own browser separate from Firefox. ("Separate" as in "different stewardship". I don't mind if Firefox and Servo share some code in the form of library crates.) If there was someplace I could donate to support both Rust and a freedom-respecting web browser, that place would get a whole bunch of money from me.
- Strom 6y agoImproving Rust itself is already a humongous task with no shortage of issues to solve. Taking on something as big as Servo on top would be a horrible distraction.