 Mele20Premium join:2001-06-05 Hilo, HI kudos:4 | reply to MagnusM
Re: Oracle Java SE 7u9 and 6u37 released said by MagnusM:said by gugarci:Is there some kind of list on the net that will tell you what programs or types of sites use Java? If you're asking this you probably don't need Java installed at all I don't need Flash Player but Java I require. I have software (paid software) that requires Java. Java is a LOT more important than is Flash...that is the one I can do without.
I use very old versions of Java on my Host machine and my virtual machines. I am upset with Mozilla because it blocked my Java on Fx and SM and I can't unblock it. So, I have to use IE for Java or use an old version of Opera where Java is built in as the latest Opera blocks my old Java versions. I can take care of myself security wise. I don't need my browsers acting as though I am an ignorant of computers user that they need to protect.
I'm waiting on my new computer to arrive. I'll be installing Java on it and then upgrading my paid software (have to pay for the upgrade) that uses Java. So, I don't understand people saying they don't need Java. -- When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson |
|
 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 3 edits | The browsers didn't block your very old Java 6 update 7 from 2008. It stopped working a couple years ago, before the security blocks started, because browsers adopted a standard API to work with Java that your old Java version doesn't use. That's why you can't unblock it, it's a compatibility issue not a block issue. »java.com/en/download/faq/firefox···ugin.xml
said by Java website : Starting in Firefox 3.6, Mozilla foundation will drop support on OJI (Open Java Virtual Machine Integration) and will only support the standard NPAPI and NPRuntime interfaces. The Java Plug-in which is in Java version 6 update 10 or newer versions supports the NPAPI and NPRuntime interfaces. Therefore, starting with Firefox 3.6, Java-based applets will NOT work unless you are running Java version 6 Update 10 or newer.
-- If it's important, back it up... twice. Even 99.999% availability isn't enough sometimes. |
|
 Mele20Premium join:2001-06-05 Hilo, HI kudos:4 | No, my Java worked just fine on Fx, SM and Opera until the browsers blocked it about a year ago. These older versions still work just fine on IE 6 and IE 8. Mozilla says it has blocked my Java and says I can unblock the block but it doesn't unblock. So, if Mozilla did not block it then why do they claim to have blocked it?
I never used Fx 3.6. I had Fx3.0 on a virtual machine but TBE didn't work on it much better than on Fx 2 (where it didn't work at all with out several hacks that I had to use). I continued to use Fx 1.5 (best version of Fx ....after that it has all been downhill) on the host machine until Fx 4 was released (and made Opera my default browser for two years). On my virtual machines I had Fx 3.0 and Java worked fine until I upgraded to Fx 10 ESR which is unstable and not nearly as good as Fx 4 (which isn't as good as 1.5).
Java continued to work on Opera until recently. Now, I just start an older version of Opera. (Current version is the worst version I've ever had and I've used Opera since version 3).
My old Java works on IE6 and IE8. Of course, what I really wish I still had was Microsoft's Java Virtual Machine. I NEVER touched Sun Java until Microsoft was forced to kill their Java which was superior to Sun's. -- When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson |
|
 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 2 edits | You may have had a slightly newer version. Java 6 update 10 did use the new API and would've worked until browsers started blocking it for security reasons.
Firefox 3.6 used the new Java API and required the use of Java 6 update 10 and up.
Many of the other browsers switched to the new APIs and needed the same Java versions around the same time frame. Making a single Java release usable by multiple browsers was easier to support than coding individual versions of Java for each browser. |
|