@ulatekh Coding style, especially in a language like C++, is wide open to interpretation and variation.  We could use camelCase, lpHungarianNotation, or some_other_style_.  If every developer used whatever style they wanted, the code would be harder to read because it wouldn't be consistent from module to module.  In fact, mixxx already has major problems because of this (the vinylcontrol code, which I'm in charge of, comes to mind :/).

Therefore, style is actually a pretty important part of our review process, and we're actually a lot more lax than other organizations.  We don't enforce column limits, we allow lone braces on following lines, etc -- even though it might help readability to be more strict.  The old adage applies: code is read more often than written.  As a project that is starting to get quite large and with a large developer community, having a core style is becoming more important.  So while it's absolutely true that RJ's suggestions are functionally equivalent to what you wrote, there are two more important things to keep in mind:  1) RJ is not criticizing your ability or opinions directly -- there's nothing personal involved; and 2) RJ knows how most of the code looks in mixxx and knows what we other developers are used to seeing.  I know it's difficult to slog through a *ton* of comments that seem nit-picky, but the result will be more consistent code for everyone to read.  

I understand that you might prefer certain patterns, and goodness knows there are some patterns I'm asked to write in my paying work that I don't agree with, but we have good reasons for asking for the style changes we ask for and we hope that you can give us the benefit of the doubt and roll with the nitpicks.  If you feel like we're removing some evidence of your personality from your code, that's not entirely false -- we'd like all of the code to feel like Mixxx code, regardless of which developer wrote it.  But the upside is that the codebase feels more cohesive and is easier for others to learn.