1. Euphoria and Mac OS X
Hi all,
Just quick question. Is there any possibility that Euphoria will be ported
to the Intel-based machines running Mc OS X?
Regards,
Darek
2. Re: Euphoria and Mac OS X
darek wrote:
> Just quick question. Is there any possibility that Euphoria will be ported
> to the Intel-based machines running Mc OS X?
I'm not working on it, and I don't know of anyone who is,
but it should be fairly easy for someone with a bit of
C knowledge, and $79.
http://www.rapideuphoria.com/reg.htm
It shouldn't require many changes from the Linux/FreeBSD
versions of Euphoria.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Euphoria and Mac OS X
- Posted by D. Newhall <derek_newhall at yahoo.com>
Aug 11, 2006
-
Last edited Aug 12, 2006
Robert Craig wrote:
>
> darek wrote:
> > Just quick question. Is there any possibility that Euphoria will be ported
> > to the Intel-based machines running Mc OS X?
>
> I'm not working on it, and I don't know of anyone who is,
> but it should be fairly easy for someone with a bit of
> C knowledge, and $79.
>
> <a
> href="http://www.rapideuphoria.com/reg.htm">http://www.rapideuphoria.com/reg.htm</a>
>
> It shouldn't require many changes from the Linux/FreeBSD
> versions of Euphoria.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Now I (usually) keep my criticisms to Euphoria to as minimal a level as possible
but this is the one "ROB! YOU ABSOLUTELY NEED TO CHANGE/ADD THIS FEATURE OR
EUPHORIA WILL *DIE*!!!1" comment that I hold to be absolutely vaild.
I LOVE Euphoria.
I LOVE the Mac.
Which do I choose?
I have a Mac, I work for a company that uses a lot of Macs, and once out of
school I'm working for a company that develops Mac apps. Windows is pretty much
dead to me (I dual boot for a few games and Euphoria).
The sole reason I will not upgrade to 3.0 is that there's no Mac support and I'm
changing jobs. I'm completely stuck (willingly and happily) with a Mac for both
work and pleasure. Currently, I can use Euphoria for scripting at work (we use
Linux servers) but this time next year the only computer I have will be a Mac.
Now, yes, I can dual-boot Windows and Mac OS X on my computer (and do) but if I'm
forced to restart my computer just to use Euphoria than good-bye Euphoria.
The breakdown of OS usage goes Windows > Mac > *nix. You support two very nice
*nixes (Linux and FreeBSD) but adding all desktop and server users of those OSes
still amounts to less than Mac OS X (3.4% versus 2.9%). Why do you support Linux
and BSD but not the more popular OS? Isn't it in your best interest commercially
to port Euphoria to it? If I was arguing that you should port Euphoria to VMS
then, understandably and rightly so, you could brush me off but I'm arguing that
the second most popular OS in the world get a single port of a nice programming
language.
You could also say (like above) that I could buy the source and port it myself
but I must ask why should I? I don't see how me paying you money so I can work
for hours porting it to helps me in any way. It's possible to survive without
Euphoria and it's a commercial language (one doesn't pay Wal-Mart to move into
their hometown if they think it'd be good for Wal-Mart's buisness do they?). I
also severely lack the time to embark on such a project since I go to college and
work. If anything went wrong I'd have to analyze the source code figure it all
out and try to fix it between classes and working. You are busy with work too,
this is true, however, Euphoria IS your work. Plus, if I had the time to port a
language I would port an open source one instead since it'd involve the same
amount of work but without me paying $80.
In summation, I sincerely hope you'll take this into account and work towards
producing a version of Euphoria for the Mac because otherwise I (and others) will
be Euphoria-less and neither I nor you I suspect want that.
4. Re: Euphoria and Mac OS X
Porting euphoria to Mac OS X imply that Robert buy a Mac to test it.
I Agree that Apple made a good move by switching to a BSD based OS and my next
computer will probably be an Apple. (If it was not for professional reasons would
have switch off windows for a long time.)
Concerning euphoria development and RDS future. I've been working with that
language since version 1.2 and I think the language deserve better than what it
gets now.
I don't know the facts about RDS but my guess is that it's not worth the
investment in time and money for Robert to port to Mac OS X.
I don't think it would improve its earning from it.
What kill euphoria is that it is a propriatary language (There is so much good
open source alternatives.) My guess is that if Robert is still working on
euphoria development after those years is not for financials reasons.
Such a qualified professionnal could do a better living by working at something
else as there is high demands for such qualifications.
regards,
Jacques Deschênes
D. Newhall wrote:
>
> Robert Craig wrote:
> >
> > darek wrote:
> > > Just quick question. Is there any possibility that Euphoria will be
> > > ported
> > > to the Intel-based machines running Mc OS X?
> >
> > I'm not working on it, and I don't know of anyone who is,
> > but it should be fairly easy for someone with a bit of
> > C knowledge, and $79.
> >
> > <a
> > href="http://www.rapideuphoria.com/reg.htm">http://www.rapideuphoria.com/reg.htm</a>
> >
> > It shouldn't require many changes from the Linux/FreeBSD
> > versions of Euphoria.
> >
> > Regards,
> > Rob Craig
> > Rapid Deployment Software
> > <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
>
> Now I (usually) keep my criticisms to Euphoria to as minimal a level as
> possible
> but this is the one "ROB! YOU ABSOLUTELY NEED TO CHANGE/ADD THIS FEATURE OR
> EUPHORIA WILL *DIE*!!!1" comment that I hold to be absolutely vaild.
>
> I LOVE Euphoria.
>
> I LOVE the Mac.
>
> Which do I choose?
>
> I have a Mac, I work for a company that uses a lot of Macs, and once out of
> school I'm working for a company that develops Mac apps. Windows is pretty
> much
> dead to me (I dual boot for a few games and Euphoria).
>
> The sole reason I will not upgrade to 3.0 is that there's no Mac support and
> I'm changing jobs. I'm completely stuck (willingly and happily) with a Mac for
> both work and pleasure. Currently, I can use Euphoria for scripting at work
> (we use Linux servers) but this time next year the only computer I have will
> be a Mac. Now, yes, I can dual-boot Windows and Mac OS X on my computer (and
> do) but if I'm forced to restart my computer just to use Euphoria than
> good-bye
> Euphoria.
>
> The breakdown of OS usage goes Windows > Mac > *nix. You support two very
> nice *nixes (Linux and FreeBSD) but adding all desktop and server users of
> those
> OSes still amounts to less than Mac OS X (3.4% versus 2.9%). Why do you
> support
> Linux and BSD but not the more popular OS? Isn't it in your best interest
> commercially
> to port Euphoria to it? If I was arguing that you should port Euphoria to VMS
> then, understandably and rightly so, you could brush me off but I'm arguing
> that the second most popular OS in the world get a single port of a nice
> programming
> language.
>
> You could also say (like above) that I could buy the source and port it myself
> but I must ask why should I? I don't see how me paying you money so I can work
> for hours porting it to helps me in any way. It's possible to survive without
> Euphoria and it's a commercial language (one doesn't pay Wal-Mart to move into
> their hometown if they think it'd be good for Wal-Mart's buisness do they?).
> I also severely lack the time to embark on such a project since I go to
> college
> and work. If anything went wrong I'd have to analyze the source code figure
> it all out and try to fix it between classes and working. You are busy with
> work too, this is true, however, Euphoria IS your work. Plus, if I had the
> time
> to port a language I would port an open source one instead since it'd involve
> the same amount of work but without me paying $80.
>
> In summation, I sincerely hope you'll take this into account and work towards
> producing a version of Euphoria for the Mac because otherwise I (and others)
> will be Euphoria-less and neither I nor you I suspect want that.
5. Re: Euphoria and Mac OS X
Since Rob doesn't care to port to the MAC and someone
buys the source porting the code to the MAC.
Wouldn't that mean they could sell the port and make
lots of money.
Bernie
My files in archive:
WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API
Can be downloaded here:
http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
6. Re: Euphoria and Mac OS X
Bernie Ryan wrote:
> Since Rob doesn't care to port to the MAC and someone
> buys the source porting the code to the MAC.
>
> Wouldn't that mean they could sell the port and make
> lots of money.
Yes.
They could sell or give away the Mac interpreter executable file
to anyone who wanted it. (They couldn't,
of course, give away the source.) And in your case,
since you already purchased the source a while back,
it would just be a $39 upgrade. Your knowledge of C
is more than enough to do the job. It would probably
take you less than a month, maybe even less than a week,
working an hour or two per day (though I can't guarantee that.)
You'd start with the FreeBSD #ifdef's, and add
a few more for the Mac. I could answer a few questions
if you got stuck, but you'd have to do most of the work.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
7. Re: Euphoria and Mac OS X
Bernie Ryan wrote:
> Since Rob doesn't care to port to the MAC and someone
> buys the source porting the code to the MAC.
> Wouldn't that mean they could sell the port and make
> lots of money.
> Bernie
Why worry about a Mac OS X port when you could just install Windows or Linux on
your Mac with the Bootcamp bootloader or run it alongside Mac OS with the
Parallels virtualization product. 
Just my two cents.
Regards,
Vincent
8. Re: Euphoria and Mac OS X
Let's look at this realistically:
Rob would have to port the Interpreter, Binder-Shrouder, Eu2C Translator and the
PD Eu source to the Mac, plus keep them all updated with each new release.
Windows + Mac + Linux + FreeBSD
It apparently is already rather difficult with the platforms already supported,
and not much of a cash incentive either.
Anyone else who did the porting would be in a not very good situation, since
someone wanting to use Eu on the Mac would only be able to use the Interpreter,
not the Translator or Binder.
Jeremy
