Hi darth_mikey, alanrf and The Spirit,
Let us shove emotions aside and let us look at the facts as they are presented to us. Browser security can be adopted in two ways by settings and automatically so using specific knowledge about what threats there are around the corner, when you use this insecure tool by default on the Internet.
The developers of these tools have been making tools with a lot of features, but security came into the bargain at a very late onset, so to say. Concluding the contents of this thread and listening to and knowing the lines of his contemplation, I think this is the line in which darth-mikey would operate to establish browser security. That is the model that suits him best.
On the other hand this is not the model that can be used for the average user. They lack the insight to take security measures on the OS level into their own hands (limited rights, checks for what is allowed to run (ActiveX, BHO's, toolbars, handling of messages etc. etc.) and here the use of NoScript and/or Abe can be helpful, where in the old days we had things like Privoxy and other external filtering systems, limiting of insecure redirects etc. can enhance security. This is another model alltogether and if that could be achieved on the fly and in the background like for instance an extention like Firekeeper does it, it could help a lot of users. It is a pity I tell this only for a fraction of the general user community, because the larger part of them are not aware and have the opinion a browser is only for fun and security should be provided by others. I think therefore as you listen here carefully to what is being told, there really aren't that many conflicts only the methods to achieve this secure situation may differ, but they can also enhance each other,
polonus