You forgot 'Soylent green'... :)

You mean losses due to http://en.wikipedia.org/wiki/Hollywood_accounting don't you??

I think the biggest problem with Java is the memory bloat. A lot of the developers that work with Java have a very limited understanding how things work under the hood. This usually leads to programs that include references to "good to have" packages/frameworks that contain some functionality they need which in turn leads to memory bloat. If you then have a java-program that needs to run in multiple instances you don't gain the functionality of one memory-image many processes most OS's support. (One of the core-features that Dalvik has if I remember correctly).

Since Java have GC a lot of Java-folks seems to think memory use isn't something you should care about since the "GC" can handle it for them. This leads to bad coding-practices. No matter the language you should always know the scope of an objects life.

IMHO it doesn't matter what language you are using as long as you know what you are doing. Java often get "bashed" from C/C++ programmers but I think that's because Java as a language has a lower threshold with regarding to prerequisite knowledge about CS and is easier to learn, which produces programmers that thinks about computers as a mysterious black box that "just works (mostly)" and the code reflects that in functionality and poor performance.

Buying iPad's isn't a substitute for proper EFB's (http://en.wikipedia.org/wiki/Electronic_flight_bag), but I guess it will help with the amount of documentation in dead-tree form the pilots have to lug around.

It's a cheap solution that will work in some situations, but if they buy a proper EFB-solution they will get a much better ROI.

Here's one manufacturer of EFB's if want to read up on some of the capabilites EFB's have: http://www.navaero.com/

Companies usually doesn't mention competing products in a denigrating way for a reason and it's called lawsuit.

So, please provide a link to a car commercial doing this or stop posting please.

There, fixed it!

Some banks in Sweden signs the online-transaction with a key generated by a standalone card reader where you enter a security token + date + amount + pin. The key generated is unique for your specific transaction and cannot be hijacked.

The downside is that there's a bunch of numbers to input on the card reader but I would say it's almost foolproof security-wise.

Obligatory: http://www.savagechickens.com/2010/11/bad-people.html

In other words the "scientists" are sloppy and they produce results that fit their pet theory... Nothing new really, been going on for a long long time.

It's troubling though that it's so widespread but I guess most of them need to produce results so they can justify their need for money/tenure etc. and that usually means taking shortcuts and fudge the data.