The go-mono site reports that the Mono JIT on the PowerPC was able to successfully run the Mono C# compiler to build its first programs. This is by no means complete (exception handling is missing, and Boehm GC seems to fail on MacOS X), but it is getting there.
Mono on PowerPC Progress
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
when I see user apps, or GUIs using it. until then I have m Python 🙂
when I see user apps, or GUIs using it. until then I have m Python 🙂
Using that logic, no one would ever used C++ then.
One thing that will be interesting is the SWT for C# port and the port of SharpDevelop to SWT.
http://www.myoe.org/
This is one – there are more.
From what I understand, right now, every possible C# program can be decompiled all the way back to its source code (not just MSIL). Is that true? Of course this is irrelevant to open source development.
every unobfuscated .net program can be decompiled back to il and from il you can make a reasonable re-construction of the c# source. The same is true of java byte code. There are a number of code obfuscators available for both environments.
according the website, myOE is Windows only…
this is about MONO on PowerPC, or am I missing something?
from the FAQ:
Why Windows?
Because we like Windows, don’t you?
oops, I withdraw that last comment.
The original post was aimed at C#, not Mono. My mistake.
well, I am not some ISV so I don’t think I will be that big of an impact 🙂
well, I was making the comment in the context of this article so your original comment is accurate.
Man, I can’t wait for them to port it to MacOS X, so it should be make easier to port it to FreeBSD.
myOE doesn’t look that it has that great of an interface, granted it does look like it can do a lot, but still It could use some improvements in it’s interface. Still it’s for Windows.
I don’t see any real usefullness to writting a Mono/DotGNU application in C# when we have Cocoa/Objective-C which you can write much better applications in a shorter amount of time much easier than you can with C#.
C# seems like it has many limitations in comparison to Objective-C/Cocoa API. The best reason to write .Net/Mono/DotGNU apps is for web services and people are mainly using Java for that.
Im not trying to be a flammer here, it’s just that I don’t see benifets to writting apps for Mono/DotGNU when there are better/faster ways of writting good apps on your system.
C# seems like it has many limitations in comparison to Objective-C/Cocoa API. The best reason to write .Net/Mono/DotGNU apps is for web services and people are mainly using Java for that.
There’s a couple of disadvantages to using Objective-C and Cocoa…
Firstly, C#, being based loosely upon C++ and Java is much more familiar to most developers than Objective-C. (Objective-C has some very strange OO syntax if you’re used to the C++ way of doing things. Note that I said strange if you’re used to C++, not better, not worse, and not necessarily strange if you’re used to a SmallTalk-ish language.)
Secondly, Cocoa is only supported by MacOS X, which is not a very large userbase in comparison to what .NET supports. Sure there is the GNUStep project, which implements a large subset of Cocoa and its predecessor OpenStep. However, GNUStep is chasing tail lights, just like Mono, and Apple definitely has a history of using its legal department in these sorts of matters.
Now if you had said that Java or C++ and wxWindows offered a better alternative to C# and .NET I would buy that. Cocoa, as nice as it is, just isn’t even an option for most programmers. We don’t all have Macs, in fact, less than 5 percent of us do.
“Secondly, Cocoa is only supported by MacOS X, which is not a very large userbase in comparison to what .NET supports. Sure there is the GNUStep project, which implements a large subset of Cocoa and its predecessor OpenStep. However, GNUStep is chasing tail lights, just like Mono, and Apple definitely has a history of using its legal department in these sorts of matters.”
Apple is not the only one who uses their legal deparment. MS’s cooperation with others even those they onced called partners is not exactly stellar either.
The SharpDevelop port to SWT appears to be dead until at least 1.0 comes out – or at least the SWT mailing list has been dead. Someone at mono’s blog site (monologue) had mentioned that ideas were being thrown around for a gtk# based IDE. Let’s hope that it’s not a case of “Not Invented Here Syndrome” and that they at least re-use chunks of SharpDevelop.
Apple is not the only one who uses their legal deparment. MS’s cooperation with others even those they onced called partners is not exactly stellar either.
I didn’t imply that Apple was the only company that made extensive use of their legal department. I will acknowledge that MS is just as bad on these matters.
However, use of Cocoa work-alikes such as GNUStep is no more free and clear than Mono. I just wanted to make sure everybody knew that.
GNUstep (at least core people) has no intention to chase OS X’s tail.
The goal is to be compatible with old existing OpenStep and to
have its own extensions. GNUstep will define its own future and OS X
compatible will never be the primary goal.
I’ve been checking up on Mono’s PowerPC status for some time, so this is awesome to see it making progress.