I agree. There should be three main aspects of a web browser's development team's plan.
1. Stability and Features
The browser should be stable and free of major bugs, reasonable feature requests should be fulfilled when fairly trivial or found to be important. Programmers should be knowledgable in the language the browser is in. Personally I'd write it in C++/wxWidgets, using Blink as the engine since that's the most popular and compatible renderer it seems.
2. Privacy and Security.
The user's ability to control their information should be key, and it should be kept locally unless the user explicitly chooses to send it off.
3. Customizability
The user should be able to make changes to how the browser operates through extensions, userscripts, userstyles, etc.
1. Stability and Features
The browser should be stable and free of major bugs, reasonable feature requests should be fulfilled when fairly trivial or found to be important. Programmers should be knowledgable in the language the browser is in. Personally I'd write it in C++/wxWidgets, using Blink as the engine since that's the most popular and compatible renderer it seems.
2. Privacy and Security.
The user's ability to control their information should be key, and it should be kept locally unless the user explicitly chooses to send it off.
3. Customizability
The user should be able to make changes to how the browser operates through extensions, userscripts, userstyles, etc.