[dba-Tech] Client Java is dead

Eh. The larger issue is java applets in the browser not desktop/server apps, but, even so, this is what you get when you use any framework or language that is a wrapper around the more complex underbelly of your computer and operating system. The same is just as true for the .NET framework or even my web application framework.

The real issue behind all this is:

- When you are popular, you become a bigger target. Java is a massive target.
- The nature of the company behind it. And, in this case, we are talking about Oracle. 'nuff said! :)
- The fact that it is near impossible to write perfectly secure code or design perfectly secure systems.

I don't personally have any love for Java, but I don't feel like grabbing a pitchfork and torch and jumping on the hate bandwagon, because Java isn't the real monster. Like they say, don't throw rocks when you live in a glass house. :)

Best regards,
Hans-Christian Andersen




On 22 Jan 2013, at 13:00, "Jim Lawrence" <accessd at shaw.ca> wrote:

> Client Java should be completely removed from all your clients and even
> strong Java proponents agree. Like the Flash programming language before it,
> any remotely run and updated application on your desktop is dangerous...this
> is why there are browsers. Here is a link to a good discussion on the
> subject:
> 
> http://www.javaworld.com/javaworld/jw-01-2013/130115-how-to-kill-java-dead.h
> tml
> 
> Jim
> 
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com