Re: Identical rendering? [was Re: SVG 1.2 General feedback]

Hello Vadim,


> |  VP> But SVG can be used as *final distribution* format for documents,
> |  VP> no?  I SVG can replace closed PDF at some moment.  What we need
> |  VP> for this is good, fast SVG renderer, and necessary support for
> |  VP> printers (drivers).  I can think CUPS can be a good start for
> |  VP> this.  We just need replace PS with SVG, and GhostScript with good
> |  VP> SVG renderer.
> |
> |      Well, SVG can be used in a large number of places and this is
> |  certainly one of them.  You should take a look at Batik it is
> |  currently the most conformant SVG renderer available (unfortunately
> |  for you it does not do font hinting at all).  But it is certainly
> |  capable of taking the place of a tool like GhostScript (who's font
> |  rendering is generally much worse than Batik's - IMHO).
> 
> I doubt that Batik is capable to take a place of GhostScript.
> It requires Java, it's slow, and it's huge.
> 
> Java will die in 6-12 months, unless Sun finally change its mind and make Java 
> Open-Source.**  So, it's not good idea IMO to use product based on 
> close-to-death technology.
> 
> ** C# will eat Java's lunch, as Sun is a way behind Microsoft with marketing 
> experience, and Java has no advanatges over C#.

People on this list usually have constructive discussions. Derogatory 
statements do not help making progress and heated comments on Java are 
not helping the SVG 1.2 specification.

Besides, of course, I disagree with your analysis on Java which I think 
has a long and healthy life ahead of it. Its powerful APIs and large 
number of open-source projects built on it are a few of the reasons why 
I think it will continue to be sucessful. But this list is the wrong 
place for such a debate, so thanks for moving the discussion on Java to 
some other forum where it is appropriate.

Regards,
Vincent.

Received on Thursday, 21 November 2002 06:37:20 UTC