You can't fire a faculty member because outside the scope of his duties he expresses an opinion you don't like -- even if it's a clearly crackpot opinion. If you could, Stanford would have kicked Linus Pauling out when he became a Vitamin C crackpot.

The difference, though, is that Pauling was a sincere crackpot -- brilliant people are often susceptible to crackpottery because they're so used to being more right than their neighbors. Dr. Oz is a snake-oil salesman; when he's faced with people who are educated -- not necessarily scientists but critical thinkers -- in a forum he doesn't control, he speaks in a much more equivocal fashion. That shows he knows the language he uses on his show and in his magazine is irresponsible.

So selling snake-oil isn't crackpottery, it's misconduct. But somebody's got to find, chapter and verse, the specific institutional rules of conduct Dr. Oz's misconduct violates. There will have to be due process, particularly if he's a tenured professor, which will probably require lesser disciplinary measures than dismissal be tried first.

In these situations, I'm not entirely sure collateral damage is of a primary concern. The image of either building being damaged or destroyed or the threat to elected representatives likely presents a worse impact than collateral damage might. Its like all the special protections they already have. For instance, punch your neighbor and face a misdemeanor, punch a senator or the president and it is not only a felony but a serious one at that. Kill someone in an auto accident and it can be a charge with less than 10 years but run over a police dog and you face life for killing an officer of the law.

Our system has said they are special and more protected than most people for quite a while now.

Anything is possible but they have helicopter rides at the county fair around my neck of the woods. They take off and land right next to the fair way with an area about 30 yards roped off. Of course they approach and leave from the far side and away from the rides but its usually still over a parking lot.

I'm not sure I would be overly excited about his landing. Still some concerns but likely not dangerous.

Not directly. Not as an individual. But diverting resources to quackery is bad for society; not so bad in this case that it's high on my list as "health supplements", but not totally benign either.

That's speculation. Feasibility is no guarantee of performance.

I read the attached article, and there were two specific complaints cited. The first was security, which is a non-functional requirement; that could well be a failure of the customer to do his homework on requirements but presumably a competent and honest vendor could have done a better job on security. It's often the vendor's job to anticipate customer needs, particularly in projects of the type customers don't necessarily have experience with.

The other complaint is that the curriculum wasn't completely implemented. If the vendor failed to deliver something it agreed to, that's purely the vendor's fault.

Sometimes bad vendors happen to good customers. Bad vendors happen more often to bad customers, but every project involves taking a calculated risk.

There is a surface to air missile battery on the capital building and white house. Likely in other areas around there to.

Because of his slow speed and open cockpit they had the opportunity to watch him instead of just reacting. If he got closer or appearedt to be threatening to the white house he likely would have been shot down.

Well, until the details of how the contract was awarded and how the vendor failed have been thoroughly investigated, it's premature to fire anyone.

Don't get me wrong, I'm all for accountability and decisiveness, but picking someone plausible and throwing them under the bus isn't accountability. In fact that may actually shield whoever was responsible.

They probably saw that FreeBSD has been doing it for 15 years [freebsd.org] and thought it might be a good idea.

Though I thought of this too, it's a majorly different level of parsing, and therefore much smaller attack surface.

MS has a full HTTP stack in the kernel. FreeBSD accept filters (including the http_filter) do a minimal check, then pass the full request to userspace - no heavy parsing in the kernel. I think the http_filter just looks for GET/HEAD/WHATEVER_SCHEME and a few other minimal things, and then tells httpd "here ya go"

You could have apache installed by default (witness MacOS X) and run from userspace, you don't need it in the kernel by default.

1) Literally?

2) This is actually pretty common, witness the TUX Linux kernel web server a few years ago.

Why? the same reason anything is dumped into kernel mode. Speed. Got a few thousand hits per second? Drop your userspace code into kernel space, and now you're eliminating a few thousand user-kernel space swap outs per second. Problems? Yeah, lets have a fairly complicated protocol that is designed to be poked at (and therefore hacked at) remotely dropped into the kernel. That and complicated data structures and kernel memory management don't mix well sometimes.

I agree with you. I thought TUX was a bad idea when it came out. Now imagine a new protocol without all the design bugs sorted out, without all the implementation bugs sorted out (i'm looking at you HTTP/2.0 SPDY) dropped into the kernel.. Oy Vey! the pain!

Mo money mo problems

See "Broke" from 30 for 30. Hell, see all of 30 for 30.

One of the best features of the "old" maps was the historical traffic times. Say I need to be somewhere at 10AM; I can get my route, then some clicketty-click and get what the normal transportation time, with traffic, is. Use that as a guess, with some extra slop and you;ll probably get there on time. I haven't seen this feature in the new maps.

Though hard to bitch about "you get a pretty useful GPS as a (pseudo) freebie*" I hate when Google thinks "yeah, you really want this" when I really don't. Their idea of "you really want this" tends to not be as often as they seem to think. Eg: my distaste for all things Material Design now. Too much wasted space, a big saturated color header with a thin white font inside making it hard to read, too much effort to make that little circle at the bottom right do too many things.

Anyway, rant over.

(*) Free as in "Every google app wants access to your location every second... from Maps (makes sense) Google Now (a bit more sense, but location turned off) to GooglePlus (only google engineers go there anyway) to Google Hangouts (no thanks)"