3 ms·
> 'll give that a 'maybe'. I don't see much difference in speed of development, if any I see a much slower pace of development @ Mozilla, bugs are open for a ve
by AsyncAwait 6y ago
> 'll give that a 'maybe'. I don't see much difference in speed of development, if any I see a much slower pace of development @ Mozilla, bugs are open for a very long time and are typically closed not because they got fixed but because they've been 'inactive for too long'.
This has little to do with Rust and has been a thing for a long time and honestly it's a thing for every major piece of software, you just don't see the bug trackers usually.
Just look at how many issues VS Code or IntelliJ has logged in for example.
The fact is, Firefox only got usable at v57 for many, including me, which was thanks to Rust.
> 12 people is not 'tiny', thats two full teams.
And how many marketing, outreach and happiness heroes, ambassadors etc. does Mozilla employ? My bet would be 5x the size of the Rust team at least.
- steveklabnik 6y ago(I've been staying out of all of these threads, but to be clear, the number of people employed to work on Rust by Mozilla is more like 3 or 4, not 12. It's been shrinking for quite a while.)
- AsyncAwait 6y agoMy bad, that was a pure guess, because even 12 is not much for a major language like Rust, but 3-4 is absolutely tiny.
- steveklabnik 6y agoYeah it's all good. It was that big at one point, making it even easier to think of that way.
- nec4b 6y agoThat is one dysfunctional organization if it needs to invent a new language only to have a browser that is usable but still behind its competition in functionality and speed.