Re: A Portable API for Euphoria

new topic     » goto parent     » topic index » view thread      » older message » newer message

Robert Craig wrote:

<huge clip >


> I'll be thinking about these strategic issues
> over the next few weeks. If anyone has any ideas,
> let me know.
>
> Regards,
>      Rob Craig
>      Rapid Deployment Software


                Just my 2 cents worth,
one: RDS need to keep max controll over Euphoria, it's an amazing
language and I want to keep it that way.
        Note I said controll, this isn't necesarily at odds with
release of (some) of the source code. just do it in very carefull
way, with contracts/license agreements/ threats to sue the life
outa those who don't toe the line, whatever it takes.
        (perhaps give part of the linux/mac profits to whoever does
the port, but leave yourself the rights to the language itself, and
final say over wether the port is releasable(and the right to find
a new porter if necessary))

Two: before you port the source code to other OS/CPU combo's
you might want to consider getting all the docs converted
to multiple languages to increase the number of people on wintell
machines who can use it easily this might just create a bigger market
than porting to linux/mac.
        Perhaps you could make set up a permesion to copy the manuals
for profit as long as the copies are not in any language RDS
publishess in?
        Or give full registered versions of euphoria in exchange for
translating the manuals (and maybe ed?) into other languages.
        Or somthing.

Three: I'm much more interested in a full compile ver of euphoria than
a mac euphoria. (though full compile is needed much less in euphoria
than most other languages), or possible a rewrite of as much of
the euphoria interpreter into ASM (assuming you haven't squeezed
every last bit into asm allready)

        Kasey

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu