| I don't know if your choice of words was intentional, but if I am developer and you come to confront me - I would also be more aggressive in the communication. > Every time I try to espouse an issue that I have with the design or architecture If you start a conversation with "issues that you have", you are going to have a hard time. Always. Starting with "issues that you have" is bad because (a) it assumes that you know more than the developers who have done the work of designing and addressing the trade-offs of the system and went through the actual work of developing the solution, (b) it assumes that your needs are more important than those of other users who are satisfied with the solution and (c) places the burden of solving your issue onto their shoulders while offering nothing in return. In other words: no one likes a know-it-all. If you start the conversation with the intent of understanding why things were done in a certain way and why certain design choices were made, you will be more likely to get in an engaging and productive conversation than just showing up with a laundry list of things that you'd like to see "fixed". By asking why instead of "confronting" design choices, you are more likely even to get them to recognize when a choice is sub-optimal. I follow a good part of the lead members in Brave on Twitter. I've seen a lot of conversations from them with other people. Most if not all of them are working with false assumptions and don't even bother to question themselves. Those that come right away aggressive against them or assuming malice are indeed met with brashness. It might seem rude, but I would probably do the same after fending off the 100th random person on the internet accusing you of things you haven't done or demanding that you do something about the token price. Those that come with the intent of understanding and assuming good intentions are way more likely to be treated cordially. |
This is not an issue on Firefox, Chrome, or even Safari god forbid. These browsers are the main contenders because they're simple, and just browsers. Trying to build an "everything machine" is what made Internet Explorer such an unbearable slog, which is why all of our modern browsers are defined more by their limitation than their capabilities.
Again though, these are not my problems to fix. Brave has already burned their bridge of trust by involving themselves in crypto (and pocketing a portion for themselves, worse yet), so I have nothing more to do here than kick back and watch your development slowly turn back into a Mozilla-type org again.