The scope is small and well defined and so is a welcome break from having to divine murky business requirements, slow iteration speed with microservices, and other every day fatigue.
I completely agree. It’s depressing to see the whole thing steadily come apart at the seams due to their own leadership (or lack thereof, one could argue).
Actually I realize what I wrote above is less true now as they have fired a good number of their incredibly skilled engineers, many of them of course Rust developers. So I suppose my post should be rephrased along the lines of “what Mozilla should or could have done”.
A possible alternative source of income for Mozilla I think would be, and one I haven’t seen mentioned before, providing consulting services in their areas of expertise.
For example, demand for Rust engineers seems to be steadily increasing[1] and I can’t think of a better company with a larger concentration of Rust expertise than Mozilla. Perhaps the same could work for other areas (ex frontend), but I’m biased toward Rust.
Due to lack of experience in this regard I’m not sure if this could actually work, but I could imagine allocating part of their engineering time budget to consultation, whose income would fund their core products.
[1] Besides all the articles popping up about starting to employ Rust by well known companies, my anecdote as a full-time Rust SDE is that I’m getting more and more requests on LinkedIn, and not just for the usual crypto roles.
The scope is small and well defined and so is a welcome break from having to divine murky business requirements, slow iteration speed with microservices, and other every day fatigue.