I still think that a better web browser should be made by deliberately excluding all sorts of stuff, and changing the remaining stuff. Some things won't work, but that is the necessary consequence.<p>From the previously discussions: "What specific standards would a user-respecting browser not implement?" Well, perhaps half of them, and the other half would need to be implemented differently than the standards specify. (It isn't only EME and third party cookies, but those are some of them; however, cookies is really something for the user to configure.) Some of the things that the specifications do say but are not implemented though, might be good ideas, and the web developer window is also part of being user-respecting feature (I use it a lot since the modern web is too messy to not use it; this is as a end user rather than as the web developer), but there is a lot more needs to be changed too.<p>I don't upgrade the web browser due to not wanting all of the new stuff they put in, and sometimes they remove stuff which ought to be included, too, anyways. If they actually do it good, then we can fix this, though.<p>And, those who want to consider making some new web sites should consider if plain text, NNTP, etc is suitable, rather than a web interface which is impossible to use (not all of them are (sometimes it is implemented properly), but it is common for things to be made badly). (Sometimes the API helps though, if it isn't too complicated.)<p>Also ensure that specifications are available with simple formats, so that you do not need an existing implementation just to access it.