I do think your nationalism ruins things a bit. At one point a NASA guy said it was "all about America" in a room full of US flags. Funny, I thought it was all about Pluto. Can't it just be a victory for human ingenuity and curiosity?
Where are my mod points! This should score +10 Insightful.
How is that different from today? I see that behavior regularly.
Well the difference is that today, if you take a chance and decide to do something dangerous, the other human might not have the reflexes to avoid the accident / might be in the same mood as you and might choose to hold his lane even if it means an accident. On a road with self-driving cars and human-operated cars, the self-driving ones have no choice but to choose the least dangerous behavior in every scenario. This means that humans will expect self-driving cars to behave in a predictible manner when in a probable accident scenario and this is where the problem starts, in my opinion. People will find ways to externally play the self-driving car to their benefit and then, it will become very frustrating for passengers of those self-driving cars. It will inevitably become more and more tempting for them to just disable the self-driving feature when in trafic so as to drive as aggressively as others. The only solution is to make it illegal to disengage the self-driving in non-accident situations and to have hefty fines for people gaming self-driving cars (perhaps by having obligatory dashcams on each of them).
When you have a mix of self-driving and human-operated cars on the road, the self-driving ones better have some extremely conservative defensive driving skills.
Also, expect humans to try and game the self-driving car to their benefit in trafic situations. Can't wait to see the behavior of people once they read that "changing lanes with a self-driving car parallel to you is as simple as trying to ram it - it will apply emergency brake and let you pass."
Not correct. You are referring to Mailbox Database log files (which are cleaned automatically on nightly backups). I am talking about performance counters, verbose SMTP logs and similar which Exchange 2013 has loads of.
Performance counters are not stored by default. You have to turn them on manually. Complaining about a logging feature that you enable yourself is... weird. Verbose SMTP logs are the same thing. Exchange has loads of ways to debug what's happening at each component, which is great. I have no intention to promote Microsoft's products, but complaining about features that a sysadmin typically enjoys because it opens the otherwise closed black box is contrary to general IT concensus.
There is a such thing as excessive logging. Often it can actually cause you to miss important events in the noise. Just imagine:
Cylinder 1 fired, Exhaust valve 2 opened, intake valve4 opened, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, ad nausium, engine on fire, blah, blah, blah, shutup compression filter,blah, blah, blah, blah, blah blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, relax will ya? blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, get over it, blah, blah, stupid filters are stupid, blah, blah, blah, blah, blah, blah, blah, blah, blah,, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah, blah.
Yes, excessive logging can be a problem to the person searching through it, but not really for the system itself. Yes, there are cases where it will negatively impact performance, but I am pretty sure it is not the case on any default Windows installation being put in use for typical use-cases. A car sending chatter like you mentioned on a debug bus wouldn't be a problem (and it isn't) because debug hardware is only used by experienced persons with adequate understanding to apply filters on the logging being broadcast. So, I still am not convinced that "excessive" logging is a bad idea. It certainly is much less worse than not logging enough, in which case information *is* lost forever.
You think that is bad? Try installing new versions of Exchange server. We had to add 100GB of disk space just to hold the log files of one week (plus a job to delete them after that).
You must be a pretty poor sysadmin since Exchange Log Files have absolutely nothing in common with logfiles per se. They hold transactions and their contents and are merged in the database when you do backups of the store. If you never do any backup with the proper APIs, then you'll have a big problem down the road. Also, deleting them is the worst thing I ever read.
The algorithm for finding the longest path in a graph is NP-complete. For you systems people, that means it's *real slow*. -- Bart Miller
