Date: Fri, 18 Jan 2013 03:55:45 -0800 (PST) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-ports@freebsd.org Subject: Re: www/opera ISSUE Java Plugin missing Message-ID: <1358510145871-5778824.post@n5.nabble.com> In-Reply-To: <50F8BA31.8090709@gmail.com> References: <CACGq7x36hROmEwYS75YZM1o=c7R4kpWX3thmT_J-7=CRz=zQWw@mail.gmail.com> <1358468373919-5778675.post@n5.nabble.com> <50F8BA31.8090709@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You are missing my point. Opera couldn't just outright stop 'supporting' Java plug-ins (more like Java content, believe it or not, but using plug-in or JRE is secondary here), but they are not ones responsible for this environment deployment. I know FreeBSD as a project should document to the it's best ability all possible use cases one could be forced into (including using Java plug-in). I think it does good job mostly. <rant> That doesn't stop me from a little rant on the side, though... And hopefully it goes my way: http://w3techs.com/technologies/details/cp-javaruntime/all/all But that doesn't stop people from installing plug-in en masse, which starts to defy reason: http://www.statowl.com/plugin_overview.php <rant/> -- View this message in context: http://freebsd.1045724.n5.nabble.com/www-opera-ISSUE-Java-Plugin-missing-tp5778625p5778824.html Sent from the freebsd-ports mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1358510145871-5778824.post>