New Jet, New Firefox

[Roedy Green]

New versions of Jet optimising Java compiler and Firefox browser have
just been released.

For both it is a major upgrade.

See http://mindprod.com/jgloss/jet.html
http://mindprod.com/jgloss/firefox.html

 

[Roedy Green]

I don't think the improvements in Firefox have any to do with Java,
except that the rendering engine is supposed to be a lot faster no

Java and browsers are like ham and eggs.

One odd thing about the new Firefox is it seems to render a far
greater part of the Unicode set than I expected. See
http://mindprod.com/jgloss/hexentities.html
to see what I mean.

 

[Roedy Green]

One odd thing about the new Firefox is it seems to render a far
greater part of the Unicode set than I expected. See
http://mindprod.com/jgloss/hexentities.html
to see what I mean.

I think what it must be doing is checking to see if a char is
available in the given font, and if not, uses a backup font. This is
not strictly kosher, but makes sense now we have some CPU power to do
it.

Maybe Java could get this too.

 

[Arne Vajhøj]

Java and browsers are like ham and eggs.

You mean that people eat both ham and eggs but not together ??



Arne

 

[Roedy Green]

You mean that people eat both ham and eggs but not together ??

no. In North America they are commonly eaten together, just as Java
and browsers often work together, either with Applets or with server
side code.

 

[Arne Vajhøj]

no. In North America they are commonly eaten together, just as Java
and browsers often work together, either with Applets or with server
side code.

Applets are pretty rare today.

Server side Java and browsers are nicely separated by
various standards.

Arne

 

[Roedy Green]

Server side Java and browsers are nicely separated by
various standards.

That would be nice, but Ajax has undone that work.

 

[Arne Vajhøj]

That would be nice, but Ajax has undone that work.

No.

AJAX still uses HTTP, HTML, XML etc. and there are no
coupling between the JavaScript running client side
and whether the server side is PHP, ASP.NET or Java EE.

(except if you use GWT and its RPC mechanism)

Arne

 

[Roedy Green]

AJAX still uses HTTP, HTML, XML etc. and there are no
coupling between the JavaScript running client side
and whether the server side is PHP, ASP.NET or Java EE.

However the server has to be aware of the flavour of JavaScript on the
client and adjust the code it sends to dodge its bugs and
eccentricities. The blood-brain server-client barrier is anything but
clean.

 

[Arne Vajhøj]

However the server has to be aware of the flavour of JavaScript on the
client and adjust the code it sends to dodge its bugs and
eccentricities. The blood-brain server-client barrier is anything but
clean.

That is not how it is done (usually). The server send the same
JavaScript to all clients and the JavaScript itself tests
on what browser it is.

Arne