Years ago I was taught the saying:

There was another one last week that was an "introduction to programming in Swift" - which was neither.

Where in TFA is Swift actually used? All I see is a simple Interface Builder example which has nothing do with Swift.

Are we going to be continually with crappy iOS articles repeating the basics of UI development just because they have the word "Swift" in them or that they are Dice based??

And another crappy article .. with Swift

Crappy articles are crappy articles and articles like these are the reason that Netcraft confirms that /. is dying.

I would have thought his imminent heart attack would figure more in his planning.

Do you mean like the inForm system from MIT?

While I'll agree with the "IAAFM" reply that simpler can be better, I'm sure these sorts of systems are the way of the future*

* for some value of future greater than today.

Why has hollywood butchered the reality periscopes in submarines? Answer that and you will have the answer to space battles depiction.

This is a business decision, not a technical decision.

However, that does not mean there are not valid business reasons for opening up your bug list.

And in fact I was trying to something similar last year. I was on a job site commissioning equipment. There was the company I was working for, the company that had sub contracted them and the client themselves. We reported bugs to an internal bugzilla system but didn't share that list with either the main contractor or the client. Both the client and the main contractor kept their own separate lists of bugs and would send us their lists when ever they felt like putting pressure on us. Of course all three lists had items that overlapped and items that were different, so it was a pain to try and match up all the issues and prioritize the work.

I suggested several times that if the client and main contractor had access to our bugzilla system (even for just this one project) then it would reduce extra work and confusion all around and make the start up procedure a smoother and reduce a lot of heated arguments. Of course the idea of other people seeing our dirty laundry was not acceptable.

To me that implies that you think that the relevant agencies aren't capable of or do not accurately map spill locations.

Then what? What do you expect to be done with the results?

Where the hell do I find a dinosaur in this day and age so that I can laser scan it?

More reasonably: one thing that leapt to mind when watching the video is that laser scanning inherently "can't see behind the curtain". So how do you generate data for all those hidden surfaces? Several of the examples in the video showed fields of rocks, and I can't imagine there would be enough time to scan the field from all possible view points that would ensure that all surfaces have been scanned. Or is this product mainly targeted at fly-throughs along well defined paths?

I also did see in one of the comments on the site that all of the video data that was shown was static IE no animation.

I don't think that's a "maybe"

The choice of what crap makes it through the submission process is amazing at times.

I really thought that was *my* bin I was dumping all that waste food into.

I just tried it on 2 different version s of OSX: 10.9.4 and 10.7.5 and confirm that they print out the "vulnerable" message