Slashdot Mirror


Novell Presents Mono Roadmap

H0ek writes "Seems Mono is still moving along in spite of the Novell purchase. They present a nicely comprehensive roadmap. You can read the official Novell press release if you're into that kind of nonsense. All I can say is, go Miguel! Don't let the Man get you down!"

53 comments

  1. So... what's the deal? by msuzio · · Score: 2, Interesting

    So, is this worth looking into for C# development at this point? Is it complete enough? I know next to nothing about C#, but I wouldn't mind learning it. I mostly do Web/Internet apps, and my flavor of choice at the moment is Java (servlets, not the horror that is EJB).

    I keep hearing about Mono lacking System.Windows.Forms -- is this a big deal? What else might it be missing (and is any of that going to be coming soon, like within 6 months?).

    I have a lot of my developers here asking about C#, and I wouldn't mind exploring it. Our enterprise division is probably going to move towards using it in new products (we mostly sell Windows-based apps), so being able to better work with their products and code might be nice too...

    So, uh... enlighten me.

    1. Re:So... what's the deal? by raimundo · · Score: 5, Informative

      I've really enjoyed using C#, I definetly recommend taking some time to learn it. Effort is underway to implement S.W.F, but GTK# is already works cross platform. With Glade and the nicely designed Glade# stuff, using GTK# is a pleasure.

      As for web development, alot of work is going into making Mono a robust web development tool. It's still in the early stages, though. Haven't used it myself yet, but Ximian is comfortable enough with it to already be dog fooding.

    2. Re:So... what's the deal? by borgboy · · Score: 4, Informative

      It [C#] is complete enough that Java(tm) is including features that already exist in C# in 1.5 - including enums, attributes, and iterator-aware looping.

      Otherwise, from a syntax standpoint, C# is pretty roughly equivilant to Java(tm). They are both OO languages (no flames about which is more OO, that's a dumb argument) that support single-inheritance, multiple interface implementation, and some component-oriented development paradigms (beans vs properties)

      C# is similiarly including more features such as anonymous methods and Generics which made it to 1.5 before C# will get them in 2.0 "Whidbey".

      I do serious, production work in both. IMHO, it isn't the language that is differentiating, it's the class libraries and the reach of the underlying platform that dictate the decision to use one vs the other.
      For Windows development, C#/.Net has a serious edge.

      For cross-platform server applications, Java(tm) is extremely strong.

      --
      meh.
    3. Re:So... what's the deal? by msuzio · · Score: 1

      My interest is less in whether C# itself is complete enough. I was wondering if the Mono implementation is going to include enough of the "goodies" that I can immediately start doing Web/Internet programming in C# using Mono only.

      I'm still not *quite* sure, but I'm tending to think the answer is 'yes'. Of course, now that I think of it, I'm not quite clear on *how* I would do this. Is there a C# equivalent to the 'servlet' architecture in Java (and does Mono include this)? Something that hopefully runs just fine under Unix and Apache?

      I suppose I should just dig around and find it. Must be a mod_dotnet out there :-).

    4. Re:So... what's the deal? by msuzio · · Score: 1

      Ah, should have just waited and added this to my post before. I see we have ASP.NET for Mono (kind of?):

      http://www.go-mono.com/asp-net.html

      Now, the next question I'll have to settle is, does ASP.NET not suck as bad as ASP under IIS used to? I never really liked the 'let's put our code in our pages' thing, I use JSPs in J2EE purely in the 'View' mode of an MVC architecture (like everyone else does, right? <grin>).

      Oh well, at least something to play with in between compiles of my 'real work'. Lets me have an answer when the PHB(*) comes by and asks me about this "...new C# stuff, shouldn't we be using that?"

      (*) Hey Tom, if you read this, I don't mean you. Oh, same goes if Rick reads this. Actually, I just made up that PHB stuff, of course we don't have any of those in our fine company :-).

    5. Re:So... what's the deal? by borgboy · · Score: 3, Funny

      does ASP.NET not suck as bad as ASP under IIS used to?
      Nope. it really does not suck. It aint perfect, but damn it's a couple orders of magnitude better than ASP.
      I never really liked the 'let's put our code in our pages' thing
      Neither did I, or many people, for that matter. That is why a lot of serious developers compiled COM components to service requests. Now, asp.net is a step further in that direction by explicitly (depending on the way you develop) separating logic from presentation via MyPage.aspx files (presentation) vs MyPage.aspx.cs files (logic). Of course, as in Java(tm), you CAN do it wrong/easy by glomming everything into your aspx pages. Bad programmer! No donught!

      --
      meh.
    6. Re:So... what's the deal? by DukeyToo · · Score: 3, Insightful

      ASP.NET is definitely ahead of vanilla ASP. It has separated code from display, which is good. It has also added web controls, which are very very powerful. It is also (mostly) compiled, which adds speed.

      However, it is still lacking in several areas:
      * lack of built-in page templating mechanism
      * datagrids are latebound (and possibly interpreted)
      * CSS support in Visual Studio is abysmal
      * the style of ASP.NET is "lots of custom pages" - it does not encourage large maintainable web sites.

      All in all, it is very "VB" - nice and easy to create something simple, but it takes some ingenuity to create a larger, maintainable product.

      --
      Most writers regard truth as their most valuable possession, and therefore are most economical in its use - Mark Twain
    7. Re:So... what's the deal? by REBloomfield · · Score: 1

      Why do you need Mono to investigate C(I'm on a Mac, I don't know where the hash key is :p) Grab yourself a copy of the .NET Framework and get coding! You'll miss out on WYSIWYG RAD (and will in Mono as well), but at least you can explore the language....

    8. Re:So... what's the deal? by doob · · Score: 1
      (I'm on a Mac, I don't know where the hash key is :p)


      Alt-3, it's not shown on the keyboard, but it's there.

      --
      In the spoon, there is no Soviet Russia!
    9. Re:So... what's the deal? by REBloomfield · · Score: 1

      # - oh yeah. so where's my pound sign then? ;)

    10. Re:So... what's the deal? by Anonymous Coward · · Score: 0

      Ximian is comfortable enough with it to already be dog fooding.

      However, Ximian's web-needs are sparse enough. If you head on over to http://www.ximian.com/ you'll see something functional, but none-too-impressive. I'd be interested to see how this fares on something a little more large-scale.

  2. "Don't let the man get your down"?? by phaze3000 · · Score: 4, Interesting

    Novell bought Ximian as much for Mono as anything else. This is a key part of Novell's future, I hardly think they are publishing the roadmap "in spite of the Novell purchase".

    --
    Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
    1. Re:"Don't let the man get your down"?? by winse · · Score: 0, Troll

      I happen to know H0ek was trolling when he wrote that.... because he is sitting next to me laughing right now.

      --
      this sig is deprecated
    2. Re:"Don't let the man get your down"?? by metamatic · · Score: 0, Troll

      More to the point, working on Mono is supporting Bill Gates' latest dreams of world domination. Killing Mono would hardly be "letting the man get you down".

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    3. Re:"Don't let the man get your down"?? by H0ek · · Score: 1
      Ha. Funny. Want to know my personal feelings regarding Novell? Check out my journal entry and decide for yourself if I'm trolling.

      Commi troll...

      --
      H0ek
      Think you're smart? Prove you've got brains!
    4. Re:"Don't let the man get your down"?? by Anonymous Coward · · Score: 0

      More to the point, working on Java is supporing Scott McNealy's latest dreams of world domination. Killing Java would hardly be "letting the man get you down".

    5. Re:"Don't let the man get your down"?? by winse · · Score: 0, Troll

      dang. i got commi'd on a slashdot thread.... I sux. Your journal entry is amuzing. I have to agree with most of what you said about Novell's past.
      I still think you were trolling a bit however.

      --
      this sig is deprecated
    6. Re:"Don't let the man get your down"?? by Anonymous Coward · · Score: 0

      Both .net and java suck. Single dispatch OO? static typing that's not even any good?

      "skinnable languages" can only take you so far. All the "skins" for .net are the same language underneath. And it's a crappy one compared to Lisp.

    7. Re:"Don't let the man get your down"?? by alwynschoeman · · Score: 1

      As far as I know Novell has J2EE interests as well...

  3. Novell Loves Mono by raimundo · · Score: 3, Informative

    Contrary to what the poster seems to think, Mono is becoming an important part of of Novell's strategy. Very shortly after Novell bought Ximian, its developers started showing up on the Mono lists and becoming involved in the community--without trying to exert any type of control. They even appear to have already started some important projects using Mono.

  4. Is Mono a death threat to Microsoft? by Captain+Kirk · · Score: 4, Insightful
    If I understand this Cringely article correctly, .Net will make Microsoft hardware independent - I, Cringely

    All of the MS products are being rewritten to be based on .Net. ISVs are being pushed towards .Net. In the case of VB developers, they simply don;t have a choice. For C++ developers, MS is constantly selling us the manageed C++ mantra. Even game developers are getting the .NEt pitch.

    If Mono works, then Microsofts own products, those of independent system developers and popular games will all be just as good on Linux, OSX, etc. as they will be on Windows. That should make MS very nervous. Go Miguel!

    1. Re:Is Mono a death threat to Microsoft? by 4of12 · · Score: 4, Insightful

      If Mono works, then Microsofts own products, those of independent system developers and popular games will all be just as good on Linux, OSX, etc. as they will be on Windows. That should make MS very nervous.

      As nice as the potential technology is behind .NET and Mono might be, I tend to be more worried that the interfaces to heavily-used class libraries and components will not be sufficiently specified. That is, not all of the behavior will be replicated if you simply drag `n drop your Visual developed application from the latest Longhorn server over to a cheap Linux box. Does that even happen in the Java world, where cross-platform portability is constantly trumpeted?

      Differentiating themselves from commodity Linux platforms and leveraging their strength in Windows seems to be more consistent with Microsoft's business objectives.

      --
      "Provided by the management for your protection."
    2. Re:Is Mono a death threat to Microsoft? by dthable · · Score: 2, Insightful

      Does that even happen in the Java world, where cross-platform portability is constantly trumpeted?

      It still exists if you just want to stick to the base functionality. The problem becomes the limited amount of control you have over your applications look and feel. To really leverage that functionality, you need to get down and dirty with the operating system.

      It still can be done (i.e. QT), but takes a huge amount of developer effort and time.

    3. Re:Is Mono a death threat to Microsoft? by arkanes · · Score: 1

      "really leveraging your applications look and feel" sounds to me like code for "it'll be ugly as shit and look nothing like the rest of my applications". Some people prefer things like Java or Qt because the app looks the same on all platforms. I prefer that my app look (and act) native on all platforms, which is why I use wxWindows. And it's free!

    4. Re:Is Mono a death threat to Microsoft? by jhunsake · · Score: 1

      Not only that, but you can use wxWindows to make it look the same on all platforms using the Gtk backend. Thus if you write your app using wxWindows, you can pick at will between making it look the same on all platforms or making it look native on all platforms.

  5. Anyone with some *BSD-specific notes? by puff+the+barbarian · · Score: 3, Interesting
    From the Mono FAQ:
    Question 52: What architectures does Mono support?

    Mono today ships with a Just-in-Time compiler for x86-based systems. It is tested regularly on Linux, FreeBSD and Windows (with the XP/NT core).

    So okay, does anybody know how well it runs on Dragonfly?
    1. Re:Anyone with some *BSD-specific notes? by wayne606 · · Score: 1

      How about non-Intel platforms? SPARC, MIPS, PowerPC, HPPA? At least one of those is definitely not going away any time soon.

    2. Re:Anyone with some *BSD-specific notes? by axxackall · · Score: 1

      It's not exactly "for Linux" if it doesn't run on non-x86 platforms. At least it's against the multiplatformful spirit of Linux.

      --

      Less is more !
  6. Hate to beat a dead horse, but.... by Captain+Rotundo · · Score: 2, Insightful

    I hold no ill will toward Ximian or Miguel, they have done great things, but I still am completely unconvinced by Mono.

    I've used Mono a little (Dashboard and others) and qutie frankly I am not impressed with C#, and I am not convinced of the "common language" nonsense. What does strike me is how it seems no different or better than the technology Java introduced years ago. Add to that the fact that I don't think anyone can successfully play catchup with MS, and that I think MS patent lawyers will pounce the second Mono looks credible to a .Net or C# developer.

    Why not re-implement a Free Java clone with the same resources. Java is more 'open' (maybe not officially with standards but in practice for sure) Java is here NOW, and Java has developers now. Not to mention the stigma of cloning MS wouldn't be there to scare away people like me. - Not to mention the things in .Net that are very windows specific that it is either hard or useless to port to a different platform (who wants a VM language that requires a windows emulator to run? why not just write a windows program and use full on Wine at that point?)

    I really hope Mono becomes something great, but I simply don't want to invest my time in a platform that appears will remain a bastard step-son to .Net for the foreseeable future. On the other hand Sun seems to have an interrest in a GNU/Linux desktop at this point, and may be coming around to wanting a full fledged java platform on Linux.

    1. Re:Hate to beat a dead horse, but.... by DukeyToo · · Score: 4, Insightful

      .NET is very Windows-UNspecific, not at all what you would expect from MS. It has some Microsoft specific stuff, (eg. accessing windows registry) but that is generally relegated to a separate "Microsoft" namespace.

      In addition, you seem to think that .NET is all about Windows Forms. It is not. For me, that is the least interesting aspect. You can write console applications, or server deamons, or web services, or DLLs for re-use by multiple UIs.

      Like Java, C# is here NOW, and C# developers are here now. As are VB.NET developers, as fast as they can convince their management to change. As a platform, .NET has a large amount of support, from the people who write software for Microsoft platforms. I assure you, there are very many.

      For myself, I develop specifically for Windows, and .NET has to be very important to my career. And Mono is too, because it opens up a whole new market for my MS-centric skills - suddenly, I have a chance of telling management that they are no longer tied to MS because their business relies on my Windows program. And that is very exciting.

      If you are a Java specialist, there is really no need to stray, for now. However, Microsoft will do everything it can to make it easier and easier for you to migrate your skills to .NET, and at some point in the future it may become worth your while.

      --
      Most writers regard truth as their most valuable possession, and therefore are most economical in its use - Mark Twain
    2. Re:Hate to beat a dead horse, but.... by Captain+Rotundo · · Score: 2, Insightful

      You made my point exactly. Your interrested in .Net because your a windows developer. There is no compeling reason to be interrested in .Net if you are not tied to the Microsoft platform.

    3. Re:Hate to beat a dead horse, but.... by Anonymous Coward · · Score: 0

      i feel like I've read this exact same post somewhere else. did you post this somewhere else before?

  7. Microsoft does not like Mono or Linux by GreatDrok · · Score: 3, Interesting

    Yeah, I know, big surprise.

    A couple of years ago I visited MS in Redmond to see if there was some way my then company could work with MS. We had a very encouraging two hour discussion and I was told that MS would very much like to work with us. I had demo'd our software on a Linux laptop running KDE (so I don't think they noticed it wasn't Windows) and mentioned that as we were a Linux based company we would use Mono to integrate with .NET. The response was "We don't work with Linux companies, I'll get you a cab" and that was that.

    While it is clear that they don't like Linux, I think it is also apparent that they will not condone anyone using Linux/Mono as a development platform instead of Windows/.NET and they will very obviously move to kill it by incompatibility as soon as it shows the slightest chance of being a threat.

    --
    "I have the attention span of a strobe lit goldfish, please get to the point quickly!"
    1. Re:Microsoft does not like Mono or Linux by zero_offset · · Score: 2, Insightful

      What surprises me is not that they sent you packing, but rather that it surprises you (apparently), and that you even bothered to try. Why in the world would you have expected Microsoft to greet a Linux-based company with enthusiasm, regardless of what you're making/selling/proposing/etc...?

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

  8. But there *can't* be a Mono roadmap by cabalamat2 · · Score: 3, Funny

    Mono is an open source project, and Steve Ballmer says open source doesn't have roadmaps.

    I believe everything Steve and Bill tell me, so this "roadmap" obviously doesn't exist.

  9. You are right by Decaff · · Score: 1

    Just look at the Mono roadmap. .Net on non-Microsoft platforms will always be just a bit (or maybe a lot) behind .Net on Windows. There is simply no reason not to use Java. With a fast VM (such as IBM's) and a decent native GUI toolkit (such as SWT) you can write full-featured high-performance applications with the advantage of portability. If you want web services, use J2EE. The next version of J2EE can provide services to .Net clients!

    You don't lose out by choosing Java, you only gain freedom from Microsoft.

  10. Java is not open! by axxackall · · Score: 1
    Why not re-implement a Free Java clone with the same resources. Java is more 'open'

    Java is open? Are you kidding?

    Without EJB Java is useless for complex applications. But with EJB all other languages are useless. I don't see any "openness" of Java here.

    With Mono I can use any other language that has a dotNet library for it. And many languages have it already. This is what I consider as "openness".

    --

    Less is more !
    1. Re:Java is not open! by mcbevin · · Score: 2, Insightful

      If Java is 'useless for complex applications' without EJB, then I'd say Java is pretty much useless based on my experiences with EJB. Luckily however, theres also a thing called JDO which does what EJBs should do, but a lot better and simpler.

      To answer those that say C# is no better than Java, I'd personally choose developing a GUI with C# + Visual Studio over Swing any day. C#'s XML handling I also find a lot nicer that any of the DOM/JAXB etc alternatives available with Java. And C#s auto-boxing and unboxing also relieves some Java-annoyance. Theres three rather improvements which have impressed me, but there are also others :).

      As a language I find C# has a few such nice improvements on Java with very few drawbacks. This has to be of course balanced with the fact that Java is a lot more mature (i.e. theres a lot more tools out there that use Java) and is not Microsoft controlled.

      Also, look out for future versions of both languages. Java 1.5 is including some really nice improvements (i.e. generics for one), as is the next .NET version. Nothing wrong with a bit of choice and competition :).

    2. Re:Java is not open! by fender_rules · · Score: 1

      What does make you think Java is less 'open' without EJB? I think Java is far more open because of JCP and third party implementations, and great number of OSS projects developed with it. Do you think Mono is an open source project? Maybe their license is open source, but they don't have any choice about .NET framework itself except for blindly copying what MS does which does not seem open at all to me. And BTW, if you really think Java is more 'open' with EJB support, you have number of open source implementation of J2EE containers out there, and some of them are production quality.

  11. JIT vs interpretation by Anonymous Coward · · Score: 0

    The situation is that JIT compilation (mono executable) is available for x86 right now. Other platforms can be supported via an interpreted version of the runtime called mint. mint is really useful as the first stage of a port since you can get the libraries up and running. Then write a JIT. I think there's ongoing work for PPC JIT.

  12. Java is open by Decaff · · Score: 1

    Java is fully open. The spec of the VM publically available, and anyone can implement a Java compiler (GNU have one - look at GJC and the Classpath project). Sun don't provide an open source Java compiler and VM, but neither does Microsoft for C#. What they do provide is a free high-performance VM for Windows, Solaris and Linux.

    EJBs (Entity Java Beans) are a very small part of Java. There are thousands of client-side applications and tens of thousands of websites that use other Java technologies such as JSP, Servlets, Applets, JNI, JDO etc. Noone could say these are anything but serious applications

    1. Re:Java is open by axxackall · · Score: 2, Informative
      EJBs (Entity Java Beans) are a very small part of Java.

      You are pretty new with java, aren't you?

      EJB stands for Enterprise Java Beans (not Entity beans, which are just a part of EJB, but not everything). The way how things are designed makes Java without EJB useless for Enterprise applications. And EJB is very far away from being small part of Java. EJB actually do help to integrate various applications in an enterprise to work together, in a same (similar) way as .Net does. Using Java without EJB for such integration is the same as writing on C++ (or even on Assembly) without .Net

      Of course you don't need neither .Net nor EJB when you develop a standalone web-site. Feel free to choose between PHP and JSP in such case. But that would be off of originial topic, I can say.

      --

      Less is more !
    2. Re:Java is open by fender_rules · · Score: 1

      I don't think developing enterprise applications or even integrating them madate use of EJB. In most of the cases, a well designed servlet-based application which is load balanced using session affinitity scales well enough. That's why many of the developers turn their eyes to such alternatives as Spring, Hibernate, JDO and etc. And if you only use session beans - which has become very prevalent design choice nowadays - it does not offer much than load-balanced servlet applications anyway.

  13. No, it will be death threat to OSS community! by fender_rules · · Score: 1

    First of all, I do think open source community should continue embracing C# as they've done in Gtk#. And I think .NET have great potential to compete with Java at server side market, and will certainly dominate Win32 desktop client market for years to come.

    However, what I strongly object is that OSS community trying to adop .NET framework and wasting their time and talent in such project as Mono.

    As you can see from the roadmap Novell published, any attempt to reimplement .NET platform will be endless game of blindly copying everything MS put into their products under the '.NET' brand name.

    Do you really believe Mono or Novell could make their .NET implementation way better than MS so, they will lead innovation of .NET technologies while MS lagging behind them struggling to make their official .NET runtime compatible with technologically superior Mono alternative?

    No, I think the other way round wil be the case. Hell... if bunch of OSS hackers backed by one company has that much power, everyone would be all using Linux, OpenOffice, FireBird, or whatever by now instead of Windows, MS Office, IE craps.

    Maybe MS will succeed taking some market share from Java, and big companies will move to their new Windows server products, so tools market, developer base will all move around their 'official' .NET platform, while Mono developers will provide their copy of MS .NET to some poor companies which can't afford to buy MS .NET and technical support.

    While they - Mono developers are up to this task, they won't make any significant innovation to .NET framework for no commercial companies will be insane enough to build their business applications using some Mono specific features(What important innovations have we over Win98/WinXP with Wine/WineX?).

    On the other hand, MS will put every non-standard features into their product which will lure more customers so make it practically impossible to copy their product like what they did with IE before.

    And most importantly, when applications like IE, MS Office, Photoshop begin to run on Mono/Linux, it will be the end of such projects like FireBird, OpenOffice, Gimp, and so on.

    Maybe OSS developers find it more easy to program in .NET than using plain C/C++ or whatever they're using today. Even some of them will start using VS.NET to program Gnome/KDE applications, and they'll more easily find jobs in MS shops with their skill in .NET technology.

    These thoughts make me shiver, and when this worst nightmare of mine come true... it will be the last day I'll still be using my Linux/Gnome desktop.

  14. ROTOR updates? by Anonymous Coward · · Score: 1, Interesting

    Does Microsoft update their open source C#/.Net that was initially released on FreeBSD, called ROTOR, along with all the new stuff they put into C#?

    (ROTOR was never meant to provide all services in the commercial .Net platform, but it was supposed to be a complete C# compiler and runtime.)

    --
    jonmartin.solaas@mail.link.no

  15. DotGNU and Mono will kill MS Windows *slowly* by bizcoach · · Score: 1
    then Microsofts own products, those of independent system developers and popular games will all be just as good on Linux, OSX, etc. as they will be on Windows.

    For Microsoft's own products, I think that this is very unlikely. MS has quite a few aces up their sleeve that they can use to use to make it very hard to use MS apps on non-MS operating systems. Games are likely to be problematic also until the marketshare of GNU/Linux on home user desktops is big enough to make games vendors care about portable programming.

    However, productivity apps will be easy to write in a portable manner, as soon as a good, portable System.Windows.Forms implementation is available, and that's why DotGNU has strong empasis in this area.

    As soon as all the apps that businesses want are available on GNU/Linux (whether via DotGNU, via Mono, or as stand-alone apps doesn't matter), we'll see lots of businesses switching away from MS Windows. People will generally want to have the same OS and productivity apps at home that they use at work if they can afford it, and since everyone can afford GNU/Linux, this will lead to the migration of many home users. I predict that this will eventually lead to the slow, painful death of the MS Windows platform.

    It should be noted however that obsolete OS platforms die slowly. Don't hold your breath.

    Also, I'm sure that MS can survive this. They're diversified enough, e.g. in the entertainment area, and I don't see how the Free Software movement could possibly kill that profit center.

  16. Corel "horse power" of Mono : LOL ! by Anonymous Coward · · Score: 0

    Corel are just a "dead horse" that are sponsorized by MS funds ey. Just look at facts.

    By the way, who care about mono ?

    Want to do cross platform ? You already got Java, it is maybe not perfect but perform pretty well.

    Want to do MS OS proprietary stuff, you got dotNet and Csharp, or whatever new stuff they will push to you, you will have to follow. Windows is their OS, they control the strategic orientation and you have to comply and apply if you want to "play" in their playground.

    Mono ? no future for this, because it become good enough one day (what it is very far from now), so that you can realy run any application on non MS OS, then MS will take whatever legal action they want to cut this opponent !

    That's why "mono" is NO FUTURE :(

    Your alternative are Java or .Net ! Sorry guys...

  17. I thought Nokia made N-gage by Anonymous Coward · · Score: 0

    From the press release:

    all supported by strategic consulting and professional services ( Novell Ngage(SM)).

    Ngage is a service mark of Novell, Inc.

    I thought Ngage was a handheld taco-phone-game-system-thing from Nokia.