Reply to thread

Message

<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1065742">Installed Brave again (in Linux Flatpak). With all bloat disabled using settings and flags. I disagree with @lnk about messing up Brave by disabling REWARDS and WALLET options (important EDIT ==&gt; thanks @Moonhoorse <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />)The chance to make code unstable by disabling options should be zero. Only when the programmers did not test it, there is a theoretical chance something messes up. But testing a disable is only one test case (as opposed to enabling stuff in which all logic paths of the enabled code should be tested). So I agree with LNK that enabling features through flags increases the chance to run into a program error (and make Brave unstable)The extra Brave functionality of rewards and (crypto)wallet is programmed ON TOP of the open source chromium browser. Normally when you re-use software and add something new, it is bad practice to inter mingle new code with existing code (always add clearly separated and modular code). Otherwise with every new release of Chromium, Brave has to regression test all use and test cases (which is simply a waist of man-power and money).&nbsp; Considering the lay-off&#039;s at Brave hardly a feasible practice IMO. Long story short: it is absolutely safe to disable stuff in settings and flags (important EDIT) related REWARDS and WALLET.</blockquote>

[QUOTE="ForgottenSeer 97327, post: 1065742"] Installed Brave again (in Linux Flatpak). With all bloat disabled using settings and flags. I disagree with @lnk about messing up Brave by disabling REWARDS and WALLET options (important EDIT ==> thanks @Moonhoorse (y)) The chance to make code unstable by disabling options should be zero. Only when the programmers did not test it, there is a theoretical chance something messes up. But testing a disable is only one test case (as opposed to enabling stuff in which all logic paths of the enabled code should be tested). So I agree with LNK that enabling features through flags increases the chance to run into a program error (and make Brave unstable) The extra Brave functionality of rewards and (crypto)wallet is programmed ON TOP of the open source chromium browser. Normally when you re-use software and add something new, it is bad practice to inter mingle new code with existing code (always add clearly separated and modular code). Otherwise with every new release of Chromium, Brave has to regression test all use and test cases (which is simply a waist of man-power and money). Considering the lay-off's at Brave hardly a feasible practice IMO. Long story short: it is absolutely safe to disable stuff in settings and flags (important EDIT) related REWARDS and WALLET. [/QUOTE]

Verification