Hopefully they will be as transparent as promised (they claimed to be releasing all of the information once the grand jury finishes).

Then we can decide for ourselves, based on that evidence. Until then, you are speculating that 'it should have gone to trial' without reasonable facts to support it.

I could speculate on reasonable reasons it didn't go to trial or rant about the media coverage emphasizing an unarmed 'teenager' ... but I'd prefer to just wait and see the facts before taking a position.

Knowing the low levels certainly can be valuable, but this example is completely flawed.

Kids are still taught algorithms and data structures, which exposes them to things like big O notation and why hash tables are really fast at lookups. They don't need to know assembly (or any specific language) to understand these logical concepts. Run time complexity like you describe is a high level concept, honestly!

It's not about shaving a few %'s off by optimizing in assembly - it's about choosing a hash table vs a linked list because you understand the logical operations needed to use them both, regardless of how 'iterating item by item' is coded in java/C/ruby, much less in assembly.

Obviously a digital version is not as good as imprinting a clone with your life's history, but give cloning a few more decades ..

http://en.wikipedia.org/wiki/C...

FROM TFA:
In another recent incident, a student posted a photo of what appeared to be a gun, and a subsequent inquiry determined the gun was fake, Sheehan said. Still, school administrators spoke with the parents of the student, who wasn't disciplined, the superintendent said. "We had to educate the student on the dangers" of posting such photos, Sheehan said. "He was a good kid. ... It had a good ending."

Errr ... so ... if it had not been a fake gun, then he'd have been ??? What if he is a hunter? Likes to shoot targets with a bb gun? Had posted a picture of his dad cleaning a legally owned handgun?? You know they'd have done something - otherwise, if he shows up and shoots ppl they'd be crucified by lawsuits.

It is now dangerous to post completely legal things .. this won't end well.

I think you mean prepared statements?

Stored procedures can be useful for certain things, but if every bit of SQL is written as one, it'll be a huge pain to read the code.

Keep things like customer_id and user_id in the session instead. That way no one can change them and submit a POST.

While harsh, this is indeed the trend that has been building the last decade. It will only accelerate going forward.

Sure, security and reliability are still huge concerns. But rather than saying 'no, we can't do that' IT will be increasingly pressured to make intelligent compromises to enable new devices and more dynamic control for engineers, designers, sales, etc ... or be replaced.

IT doesn't have to be an internal cost center either. If enough IT departments don't wake up to new requirements, 'cloud' based IT services will eat many of them for lunch. Likely not banking or governmental services ... but it will be doable for many others.

You can already do this on a smaller scale: make your own neverwinter nights or neverwinter nights 2 persistent world.

You end up with a MUD/MUSH/MUX style and size community with commercial graphics and game engine. It may be significantly smaller in scale, but it's much easier to maintain a pencil and paper style RPG world with a player cap of 64 to 96 versus a thousand. Otherwise the ratio of DM to player gets really bad or you have to have a huge DM staff that becomes hard to coordinate with ... not to mention maintain a level of quality. If the focus is on RP over grinding and huge raids, you won't want more than 6-8 players in an individual party anyway.

Shameless plug for the neverwinter nights 2 server I'm helping with: http://moonsea-adventures.com/