We've been building a suite of tools using Django that combine near-real-time event processing and offline analytics. It's been very useful and flexible; the data model abstraction is clean, and we can target different databases with a couple of lines of config file change. We're integrating some Javascript and other visualization tools in our UIs, and finding it pretty easy to support in the Django framework. Performance scales with resources fairly linearly, the overhead has been very manageable, and it integrates into almost any security framework. I've seen nothing to convince me we need to look at a different framework.

It's not the usability and ease of use - it's stupid crap like removing the ability to right-click and get a menu of things to do with that menu item, instead of just having it kicked off... it's burying the UI customization where it can't be found easily, and removing the easy tailoring options in favor of the "Unity" standard.

We just rolled back...

Correct. Falcon 9 was designed to be man-rated, but SpaceX isn't spending the money to jump through NASA's hoops until they have more of a hope of a contract for human launch services. Man rating is a high enough hurdle that LM and Boeing have refrained from man rating the Delta IV or Atlas V on their own nickels.

I was working in the first computer store in my hometown and bought it (using my wages - heh). This and Archon... I lost entire weeks to the two of them.

Someone should be auditing Apache and Linux, and it had better be the vendors making the cash off it. If Red Hat and the others aren't reviewing the code base regularly, I want to know what my support contract's paying for. I should receive an assurance that the system has been audited for most known vulnerabilities, and every patch should have eyes on it (besides the maintainer's) that look for obvious things (buffer overflows, SQL injection vulnerabilities) and oddness (the nightmare of a multi-patch Easter Egg full of badness from a malicious source).

That last bit is one of the things I have to fight most when recommending Open Source to non-techies. I've had them talk about the Jurassic Park scenario, where someone embeds lots of littls things in the code and then they know how to trigger a catastrophic reaction. The easy security vulnerabilities are treatable with monitoring and audits - it's an order of magnitude harder to audit a whole change trail.

YOU may not need a book to know this. but there are intelligent-in-their-area bean-counters who get sold on these things at major companies every year. THEY need this book, and as responsible techies, it's our job to make sure they have it. Remember, if it's in a book, it's not just OUR opinion - it's Official :)