OpenEuphoria

Regarding Dot NET

• Posted by cklester <cklester at yahoo.com> Aug 01, 2005
• 828 views

Vincent wrote:
> 
> ...there is no future with Euphoria on Microsoft Windows. The
> next version of Windows: Windows Vista, has a completely new development
> platform based
> on .NET (WinFX), while the Win32 API will still be supported (Win16 not
> supported),
> people will quickly see the advantages using WinFX and stop using the Win32
> coding
> base. By 2008, Microsoft expects that all development revolving around Windows
> will
> be .NET based, and may remove Win32.

I don't know much about dotNET. Doesn't really concern me much, yet.  I don't
see how it's going to be a radical department from the current paradigm.  But
I see that Ruby has a "bridge" for it, and looking at the code sample, I won-
der really how difficult it will be to bring Euphoria into the .Net platform.

   http://www.saltypickle.com/rubydotnet/

Please note the paragraph above is completely justified. :)

> Windows won't be so inferior to Linux anymore.

That's a good one, V!!! <wiping tears>

> That will prevent Linux or BSD from ever dominating the desktop domain.

I think (and hope) that Vista is too little too late.  M$ does have a hold
on the personal desktop,  but with more and more corporations switching to
Linux/BSD, I think that marketshare will erode over the course of the next
10-20 years. That's good news for the generation below me. :)

> There could be an Euphoria.NET, but it would have to become a full object
> oriented
> language.

Can you tell me why or point me to relevant articles?

> I probably would still prefer C# over Euphoria.NET anyway, because of the
> support for pointers and structures.

Is it because I come from a non-pointered, non-structures programming language
background that I don't find the lack of these to be issues?

-=ck
"Programming in a state of EUPHORIA."
http://www.cklester.com/euphoria/