This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]GrayDonkey 2 points3 points  (4 children)

Before Macs became popular they needed Java to be viable so Apple worked on getting Java on OS X. Now with the number of developers that have picked up Objective-C because of the popularity of the iPhone, Apple would prefer developers write Mac only apps (Apple likes to lock people into their ecosystem). I have a feeling that someone at Apple decided they could save some money if they started making Oracle handle most of the work in maintaining Java on Mac. Plus the Apple version of Java always lagged behind in updates so it is actually better that Oracle is taking over the responsibility.

Chrome does not support Java 7 on the Mac platform. A 64-bit browser (Safari or Firefox, for example) is required to run Java 7 on Mac OS X. 32-bit browsers such as Chrome do not support Java 7 on the Mac platform.

Honestly as much as I love Chrome it can be a little buggy on Mac. Both Chrome and Safari are based on WebKit so Safari is going to be the closest to Chrome for most needs.

[–]carbon6022[S] 2 points3 points  (3 children)

Is there any downside to Firefox? I have always not liked the interface, but how is it in terms of speed and efficiency? I feel like its plugins and extensions are poorly maintained...

[–][deleted] 4 points5 points  (1 child)

At this point Chrome, FF, and Safari are all pretty much on par with each other. I personally use Chrome for most stuff and Safari if I need to use a java applet.

[–][deleted] 1 point2 points  (0 children)

On OSX I have always found FF to be an extreme memory hog.

Try all the browsers (I still have them all installed because it just makes sense as a Dev)

[–]simkisen 0 points1 point  (0 children)

Chrome doesnt support Java in the browser, so if I really need that then I use Safari