672723074828

So it improves the performance for a very small number of Firefox users at the expense of the performance of all of the other Firefox users who never would have had the extension installed in the first place?

A bad thing to do is to start thinking such things to begin with. Just because somebody expresses an idea that you personally disagree with it does not mean that they are "trolling", it does not mean that the idea is "invalid", it does not mean that they're trying to "stir up shit", and it does not mean that they're trying to "kill" an open source project.

Always respond to their concerns with professionalism, courtesy, and tact.

The absolute worst thing to do is to start censoring them. I've seen this happen with a number of GitHub projects in the past. People occasionally come along with ideas that some, or sometimes even just one, of the core contributors does not agree with. Even when the newcomers are participating in good faith, I've seen intolerant GitHub project leaders start deleting perfectly good comments, closing perfectly valid issues, rejecting perfectly good pull requests, deleting perfectly good wiki content, and otherwise engaging in behavior that is much more harmful than anything the newcomer could managed to have engaged in.

When I see that happening to new contributors, especially when it's a small project involved, then I know it's time to move on from that project, both as a user and contributor. I refuse to be associated with such nonsense.

Those are absolutely awful metrics to use when measuring a developer's ability and talent, or the quality of this developer's contributions. They are also extremely easy to game, too.

This is very interesting! There is a huge difference between the assembly code generated by the C compilers and the assembly code generated by the Rust compiler for the equivalent code samples! Sometimes there is 10 to 20 times more lines of assembly generated for the Rust code than there is for the C code! The C assembly output is typically very tight while the Rust assembly output is much more verbose! Doesn't the much greater amount of Rust assembly code have a very negative impact on its performance? I just don't see how it can be claimed that Rust can be nearly as fast as C when executing the Rust assembly code requires so many times more instructions to be executed! I don't think it is a case of many fast instructions being chosen instead of a small number of less fast instructions. The Rust assembly to me just looks very unoptimized! I know Rust is a young language still but there is still a very big gap between the C assembly and the Rust assembly!

I wish that I could more easily compare the assembly outputs of the different compilers! Three or more of the rightmost panel would be superb! I want to see how the assembly compares between them without having to switch back and forth using the compiler dropdown! Make it so my good man! Make it so!