Apple vs Java

On 2012/10/24, in Philosophical thoughts, Technology, by admin


Apple doesn't like Java anymore
It looks like Apple doesn’t like Java aynmore.

When upgrading from Lion to Mountain Lion, Java was disabled from the system.

Since latest operating system update, Java plugin is disabled from every browsers.

To have it back in order, just install it from Oracle website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.

Future is not likely to fall in love again as soon as an upcoming OS update should disable Java from OS where it hasn’t been used for a while.

Apple says Java brings security leaks to its systems and disables it to avoid them.

 

3 Responses to Apple vs Java

  1. Jeffery Knight says:

    Articles like this irritate me. The number of people (IT or not) that do not understand that a MAC is a PC (regardless of what APPLE tells you) is amazing. (Off-topic I know…)

    Statements like “Java brings security leaks” is equally ignorant (I understand that the author was quoting Apple). I seriously have to somehow teach the world that a MAC is a Personal Computer (PC – DUH!) and that Java is not a plugin. I will have to troll blogs until the end of my days spreading wisdom until the masses are finally educated. Java is a programming language! That’s right! Oracle ALSO manages a Java Plugin. If you (the reader) are smart, you will proclaim that the Java Plugin brings security leaks, as opposed to Java.

    Here’s something that’s really cool: I saw the PCMatic commercial explaining that Java and Flash are security problems. I educated PCMatic that Java is not a security problem and that it is a freaking programming language!! They told me that they completely understand my position and will remove it from the commercial. Guess what???? They did! The new commercial aired this week! They do not even mention Java, Anyway… I hope my rant somehow educates the masses… and don’t worry, the MAC is still a good computer. All you have to do is install Ubuntu on it to make it worth having. Godspeed!

    • admin says:

      In this article, the word plugin was used to describe the runtime environment which allows to run peaces of Java in browsers; not at all to say the Java deployed on previous versions of OSX by default at OS level is a plugin.

      • Jeffery Knight says:

        Thank you for your response. I appreciate your attention and respect your point of view.

        I guess I do not understand what you mean when you say the “plugin was used to describe the runtime environment.” IMHO, a plugin should not be used to describe a runtime environment. The Java Runtime Environment (JRE) IS a runtime environment. The plugin is simply that; a plugin that is included as part of the (JRE) runtime environment. The plugin is a gateway into which a browser can make use of the Java runtime libraries to execute binary code (jar file) within the browser/local machine.

        Most people know that applets are risky business. If I write an applet, build my jar, sign it, place it on the web, and someone’s Java Plugin is enabled, and they accept my certificate and execute the applet, I have the ability to do harm on their system with my code (regardless of plugin vulnerabilities). If the plugin inadvertently bypasses security measures on the system to perform malicious activities, this is a fault of the plugin.

        You are correct in saying that Java installed on the OS is not a plugin. Kudos for your acknowledgment. Equally so, and it appears you may not admit, that Java does not bring security leaks to any operating system; the plugin does.

        Anyone who attempts a transitive property of equality theory to point the finger at Java (a programming language), when the plugin therein is the problem, is obviously ignorant of the Java programming language and its implementations. I apologize for being verbose in my explanation; I am sure it is warranted for some readers to comprehend the realities of the plugin versus the programming language.

Leave a Reply

Your email address will not be published. Required fields are marked *

*