However, these days, I'm also worried about exploits against browsers. If you have your system infected by just by visting a webpage, I don't consider that the

However, these days, I'm also worried about exploits against browsers. If you have your system infected by just by visting a webpage, I don't consider that the user's fault. I'm starting to consider a lot of these exploits and security problems to be the developer's fault. Too many attack vectors are well-known, and should be accounted for in the design of software. For example, overflow exploits: Why, in this day and age, do we still default to writing software that works with untrusted data in languages that don't enforce bounds checking? C++ has many virtues in many situations, but it's not a language for writing web browsers. For performance-critical modules that are small enough to make serious code auditing feasible, sure. But as the primary implementation language it's just one big vector for attack that pervades the entire codebase.