Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Sep 2010 17:23:31 -0500
From:      "Rick C. Petty" <rick-freebsd2009@kiwi-computer.com>
To:        Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc:        freebsd-java@freebsd.org
Subject:   Re: this is probably a little touchy to ask...
Message-ID:  <20100910222331.GA29252@rix.kiwi-computer.com>
In-Reply-To: <201009101658.04567.achill@matrix.gatewaynet.com>
References:  <AANLkTi=7sTm12NUdAeRrX1ZUsSveS9k7dk=hc%2BgWV9jK@mail.gmail.com> <AANLkTinmfMdYUpNGKCCAX1cE7pZJDFC07BoRsQ9XxhsA@mail.gmail.com> <86sk1hk8xa.fsf@red.stonehenge.com> <201009101658.04567.achill@matrix.gatewaynet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 10, 2010 at 04:58:04PM +0300, Achilleas Mantzios wrote:
> 
> Because tones of app(let)s were written on this technology, and those running them cannot afford rewriting them.
> its easier to just fix the plugin than rewrite every applet on earth using javascript.

Javascript doesn't provide everything that Java does, for example: threads,
socket connections, audio, file system access, native integration, etc.
Also although some implementations of javascript are quite fast, Java still
outperforms them for most operations.  Also, DOM manipulation is terribly
slow compared to Swing even.

Someone else wrote:

> > Java had its day.  Time to move on.

HTML5 can't do many of those things either.  Flash at least gives you
all of that except native integrations (which is unimportant for browsers).
Flash and Java won't go away until all of those problems are solved by
other means.  HTML5 is *not* the final solution for the web by any means.
Although, I'd take h.264 support any day over applets.  =)

-- Rick C. Petty



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100910222331.GA29252>