Slashdot Mirror

← Back to Stories (view on slashdot.org)

DotGNU and Mono Continue

Posted by ryuzaki0 on from the well-isn't-that-exciting dept.

saurik writes "After what has been a strange few weeks of converse between the DotGNU and Mono teams (including a small PR SNAFU that involved the banning of a member from the DotGNU mailing list), DotGNU has now announced that they will be forming a partnership with Portable.NET." Frankly I like that there are 2 efforts going on. Maybe one will succeed.

3 of 190 comments (clear)

  1. Re:Interesting effort... by miguel · · Score: 5, Informative
    Those statements on the FAQ are incorrect.



    We believe in writing as much code as possible in C# i
    nstead of C, because we believe we can write more code, more robust code which in the end could be reusable as a components if we use C# instead of C for pieces like the compiler and its associated tools.


    This seems to contradict what we have in our web page about the class-library. The class library is being built in a way that would allow the GUI toolkit to be plugged.



    It is also plain FUD that we do not want to make Mono work with other desktops (hey, even GNOME works on other desktops).


    You do not want to get a Gtk+ toolkit on MacOS, nor on Windows. You want to get a native interface, from http://www.go-mono.com/class-library.html:


    For classes that might differ more (for example, the implementation of Windows.Forms), we might have different directories altogether:
    System.Windows.Forms/Win32,
    System.Windows.Forms/Gtk+ and
    System.Windows.Forms/Cocoa.

  2. Re:Someone please clue me in -- why care about .NE by Ars-Fartsica · · Score: 5, Informative
    1. XML RPC. You can debate the value of XML over other RPC methods, but the .NET model appears to be simpler than CORBA and more easily extensible.

    2. Pervasive Object Model. Looking at the ActiveState site, you can see the power of being able to bind to .NET services written in any of the supported languages. Yes, you can compile Python to the JVM, but Sun won't officially support this type of activity - Microsoft on the other hand is funding cross-language support from ground zero.

    3. Mostly open architecture. C#, SOAP, WSDL, and UDDI are all open specs. Some of .NET is not open, such as the source of the compiler, but at least with a spec you can write your own, and perhaps even influence the design.

    4. A nice OO language. You get this with Java too. Hopefully memory-managed languages can become the norm for application development with all these tools available.

  3. Re:I like this concept, however... by Kerg · · Score: 2, Informative

    Sun's nursing some pretty bitter feelings right now after watching the developer community scramble to support .NET while for the most part having given Java the cold shoulder.

    I doubt Sun is nursing any bitter feelings. Their J2EE platform has more than 20 commercial implementations available, and several Open Source ones. It seems .NET has some catching up to do.

    Where's the excitement about Sun ONE?

    Well, honestly the Sun ONE looks just like a marketing effort that puts an IDE on top of the already existing J2EE platform. J2EE is the existing platform that .NET is competing against, and J2EE seems to gather plenty of excitement. It has established itself well in the market place, and pretty much taken over the application server market.

    J2EE's just a Microsoft Transaction Server ripoff

    That is not what J2EE is. If you need a comparable Microsoft platform, it used to be called Microsoft DNA, today its .NET.