9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "LiteStar numnums" <litestar@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] gs
Date: Tue,  3 Oct 2006 17:37:09 -0400	[thread overview]
Message-ID: <283f5df10610031437p7d1d35b5qca6c81f18faa2e96@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620610031348j7bb69409qc12082341f9d23e2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]

You can scratch RoPS of that list: anything that it does do, it not only
does it slowly, but improperly. To make matters worse, 'paid' version is no
better.
I had a discussion with Manfred von Thun (you know, the gentleman who
created Joy) about this while I was working on a language that was similar
to postscript & joy. He was interested in the design aspects we were
discussing, but was hesitant about the PS aspects I was using. I should
think that the real reason that PostScript is so slow is that the graphics
rely upon someone who should have really optimised some the workings out of
their source file...
Just my $0.02 (or 0.01 GBP)

On 10/3/06, Jack Johnson <knapjack@gmail.com> wrote:
>
> On 10/3/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> > out of idle interest, why has there never been a replacement?
> > is it really that hard?
>
> That's a great question.  I Googled for some leads:
>
> "Saffron includes an all-Java PostScript(r) interpreter"
> http://www.dynalivery.com/customersupport/Saffron_FAQs/SaffronInfo.html
>
> "The RoPS interpreter is a Microsoft Windows implementation of the
> PostScript programming language interpreter"
> http://www.rops.org/
>
> There is some interesting detail stuff here that I'd want to re-read
> if I were going to write an interpreter from scratch:
> http://www.anastigmatix.net/postscript/direct.html
>
> This might also make for a good jumping-off point:
> http://serl.cs.colorado.edu/~arcadia/Software/tps.html
>
> ...but from the looks of it, maybe it would be easier to "fix"
> ghostscript by making it faster/slimmer/etc.  I wonder if it runs
> better on some architectures than others?  If so, sounds like a good
> job for a cpu server.
>
> -Jack
>



-- 
If work and leisure are soon to be subordinated to this one utopian
principle -- absolute busyness -- then utopia and melancholy will come to
coincide: an age without conflict will dawn, perpetually busy -- and without
consciousness.

-- Günter Grass

[-- Attachment #2: Type: text/html, Size: 2706 bytes --]

  reply	other threads:[~2006-10-03 21:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 13:10 [9fans] OT: scsi sense error code hardware error 40 83? Axel Belinfante
2006-10-03 18:17 ` geoff
2006-10-03 20:13   ` [9fans] kenfs config? (was: OT: scsi sense error code hardware error 40 83?) Axel Belinfante
2006-10-03 21:19     ` [9fans] kenfs config? (was: OT: scsi sense error code hardware geoff
2006-10-17 15:55       ` Axel Belinfante
2006-10-17 20:18         ` geoff
2006-10-17 21:05           ` Axel Belinfante
2006-10-17 21:35             ` geoff
2006-10-17 23:55               ` Axel Belinfante
2006-10-03 20:20   ` [9fans] gs Charles Forsyth
2006-10-03 20:39     ` geoff
2006-10-03 20:41     ` Francisco J Ballesteros
2006-10-03 20:48     ` Jack Johnson
2006-10-03 21:37       ` LiteStar numnums [this message]
2006-10-03 22:07         ` Andy Newman
2006-10-04  2:18       ` jmk
2006-10-06  0:00         ` Bruce Ellis
2007-08-21 23:07 Steve Simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=283f5df10610031437p7d1d35b5qca6c81f18faa2e96@mail.gmail.com \
    --to=litestar@gmail.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).