Slashdot Mirror


Miguel De Icaza Forms New Mono Company: Xamarin

rubycodez writes "After being thrown out on the streets by Attachmate, the purchasers of Novell, Miguel De Icaza has formed a new company Xamarin to make .NET development tools for Android and iOS. The company will also provide commercial international Mono support. There are those who would say Mono poses a risk of drawing Microsoft patent or other IP litigation for its inclusion in some major Linux distributions, and that these recent events might be the beginning of the demise of widespread use of Mono and other .NETiness in open source software, a good thing."

286 comments

  1. The cross-platform .NET? by Anonymous Coward · · Score: 5, Insightful

    They failed in their first attempt at making Mono a ubiquitous development platform by keeping their mobile ports behind a paywall. Now they lost access to those proprietary parts and decided to start again, in exactly the same fashion... brilliant.

    1. Re:The cross-platform .NET? by oakgrove · · Score: 1, Interesting

      I'm not going to lie. I know nothing about C# other than the blindingly obvious, i.e., it is compiled bytecode designed to run in a virtual machine, it does automatic garbage collection, and it appears to be the premier platform for MS development. I'm pretty well versed in Python and Javascript and I've learned Java to code for Android. I really like Python and with Psycho, it runs plenty fast. And since the GUI widget toolkits like tk are compiled natively just exposing bindings to Python, the graphical presentation of applications doesn't feel slow at all (unlike Swing *ducks*). I kind of like Java too and development for Android is a breeze. Personally, I'd never use Java anywhere that Python would suffice but that is just because Python, at least to me, is so good, i.e., I think it and it almost writes itself. So, my question is this, what is so great about C# that people seem willing to practically move heaven and earth to shoehorn it in to every platform they can get their hands on. Why would I want to use mono when I can use Eclipse+Android SDK which is positively sweet. I don't get it.

      --
      The soylentnews experiment has been a dismal failure.
    2. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      cry moar

    3. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      and some spic thinks copying microsoft would ever be a great idea. dumbass.

    4. Re:The cross-platform .NET? by tepples · · Score: 2

      what is so great about C# that people seem willing to practically move heaven and earth to shoehorn it in to every platform they can get their hands on.

      What's so great is the popularity of Microsoft products in a few areas. For example, Xbox Live Indie Games won't run anything but C# and other languages that compile to .NET bytecode meeting some specific criteria. The big advantage of C# is that your video game for Xbox 360 and your game for another platform can share game logic.

    5. Re:The cross-platform .NET? by MightyMartian · · Score: 0

      Why would I want to use mono when I can use Eclipse+Android SDK which is positively sweet. I don't get it.

      Because you won't get any hot chicks?

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    6. Re:The cross-platform .NET? by oakgrove · · Score: 1

      Please enlighten me, AC.

      --
      The soylentnews experiment has been a dismal failure.
    7. Re:The cross-platform .NET? by HisMother · · Score: 1

      What part of it is wrong -- sounds 100% accurate to me.

      --
      Cantankerous old coot since 1957.
    8. Re:The cross-platform .NET? by UnknowingFool · · Score: 3, Insightful

      The problem isn't with C# itself as it is a decent language. I view it as C++ enhanced to be better than Java. The problem is Mono. Mono attempts to port the .NET framework into other platforms like Linux. While there has been a great deal of work done, it still is incomplete and missing some parts that many consider crucial. Add to that there is the looming threat of MS legal action at any time. Given the MS sabre rattling on how Linux violates hundreds of MS patents, it is understandable that some regard Mono as not safe enough.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    9. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      The difference among most languages is just syntax, which is trivial. C# + .Net's big benefit is the huge body of available code for most everything you will ever need. Amazon web services, Google services, Bing services, GIS, linear algebra, image processing, character recognition, etc. Far more than any single platform SDK provides.

    10. Re:The cross-platform .NET? by Mongoose+Disciple · · Score: 3, Insightful

      Some of it's probably personal preference -- I'd personally rather use almost anything than Eclipse, though I know a lot of people love it. (For me, at its best, it's a pair of left-handed scissors and I'm right handed, and I don't get a lot of 'best' days.)

      Some of it might be the versatility of the .NET framework with respect to language -- for example, if you prefer writing Python to Java, in theory in the .NET world you could just switch over to writing in IronPython instead of C# and call it a day, and either way it becomes .NET bytecode.

      Some of it might just be a desire for competition. For several years Java was the de facto standard for solving a lot of kinds of problems -- for example, writing custom apps for businesses. That having happened, Java as a language really stagnated in a bad way. It wasn't until C# surpassed Java (in terms of features) that Java really got going and was driven to improve again. In that sense, even if you prefer Java or something else to .NET, having .NET around will probably spur it to be better.

    11. Re:The cross-platform .NET? by solkimera · · Score: 2, Informative

      it is compiled bytecode designed to run in a virtual machine, it does automatic garbage collection, and it appears to be the premier platform for MS development.

      He's a troll. At most he can complain about you using byte code, MS calls it CIL Common intermediate language. They have their name for their VM too. But that's like saying "I'm not riding a vehicle, I'm riding a car".

    12. Re:The cross-platform .NET? by man_of_mr_e · · Score: 1

      So you complaint is that Mono isn't "a complete .net" and even if it was, then it would be bad because it's "a complete .net".

      Am I reading you right?

      Mono has addressed the legal issues by seperating the Microsoft proprietary stuff from the ISO standard stuff, and supplying non-proprietary alternatives to several parts of the system. If Microsoft sues, they can easily jettison the proprietary stuff. If you're concerned about it, don't write to the proprietary API's.

    13. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      C++ is a more expressive/powerful/complicated language than both C# and Java. The major differences (drawbacks in some applications) is that C++ does not have a large standard library, is not commonly compiled to portable bytecode and is not commonly used with a garbage collector. C# is almost the same as Java and has nothing to do with C++ except some basic similarity.

    14. Re:The cross-platform .NET? by peragrin · · Score: 1

      No Mono addressed the legal issues by having Novell work a deal with MSFT on the proprietary stuff. The problem becomes no Novell no deal, and the Proprietary stuff is required for .NET apps to actually run on windows machines. Therefore you can't build a cross platform .NET application without the MSFT side of the code to run properly on windows.

      At least that is how I remember the logic. someone can mod me down if I am wrong.

      --
      i thought once I was found, but it was only a dream.
    15. Re:The cross-platform .NET? by x*yy*x · · Score: 0

      And like you noted, .NET apps or games can be written in many different languages. He seems to like Python and that too can be used to write .NET code. All the languages can also use the huge library of code and API's. For that reason it's also easy and headache-free to write .NET apps, and for the usual languages Visual Studio is a great IDE, but there are others too. When I tried Windows Phone 7 programming a few months ago I was seriously impressed how fast the developing progress was. You can get stuff done in no time.

    16. Re:The cross-platform .NET? by UnknowingFool · · Score: 1

      No I am complaining that Mono is incomplete which I believe kinda crucial. And even if it were complete, Mono presents legal implications. If I remember correctly some of those proprietary APIs are essential to Windows. You can get around them but that means your code works differently for Windows than other platforms which defeats the purpose of being cross-platform.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    17. Re:The cross-platform .NET? by man_of_mr_e · · Score: 1

      You remember incorrectly. Mono has developed replacements that work the same on all OS's, such as GTK# to replace Windows Forms.

    18. Re:The cross-platform .NET? by DanielHC · · Score: 1

      Therefore you can't build a cross platform .NET application without the MSFT side of the code to run properly on windows.

      This doesn't sound like a problem to me... On Windows you can just use MS .NET implementation to run your applications.

      --
      Pick it Up!!
    19. Re:The cross-platform .NET? by yarnosh · · Score: 1

      As far as languages go C# is "cleaner" than Java in that many features were thought out ahead of time and not bolted on after the fact. C# also supports more language features (closures/anonymous functions, for example). But none of that is enough to make me want to use C# on anything but Windows. I hate shoehorning non-native APIs into a platform just for the sake of portability or using your favorite language.

    20. Re:The cross-platform .NET? by man_of_mr_e · · Score: 1

      Bull, you can build apps that work perfectly on Linux, Mac and Windows without using anything from the proprietary .NET stack. You use GTK# instead of Winforms, and you use Tao instead of DirectX, and you use ServiceStack instead of WCF.

    21. Re:The cross-platform .NET? by murdocj · · Score: 1

      I've programmed in both Java & .Net languages (C# & VB.Net). I'd say that advantage is that the .Net languages benefited from having Java go first. You might think of them as "Java with the rough edges taken off".

    22. Re:The cross-platform .NET? by AJH16 · · Score: 1

      Your question is more one of .Net vs a JVM. .Net is a framework. Code from any language with a .Net compiler is generated in MSIL which is an intermediate language which is then efficiently (hopefully) implemented as a complex instruction set on whatever architecture you want it to run on. This is a completely different approach from that taken with Java, which reduces everything to a super simple instruction set (originally built around a simple single register stack architecture) that can be implemented directly on any hardware architecture and then trying to figure out ways to shortcut complex functions in to the available capabilities of particular hardware architectures.

      Both systems have their advantages and disadvantages. The Java approach ends up being very dependent on trying to analyses code to find places you can make shortcuts in an automated fashion and/or adding hints to your code to optimize for a particular architecture (which throws the whole universal cross platform bit out the window). .Net avoids a lot of these issues by using a complex instruction layer that is implemented elegantly for a particular architecture, but it requires that framework to be built before any apps can run on a given architecture, but once it is done once, any .Net application will run on that platform. There are still some situation where performance can be a concern because of the level of abstraction of the instruction set .Net exposes so sometimes unsafe (ie, platform specific machine code) must be used and in this case the same holds true with it breaking the platform independence, but this is far less necessary in .Net than in Java (at least in my experience).

      For the highest performance on a particular system, your best option will still be native code compilation designed to utilize a given architecture, but with the diverse range of platforms we see today, that isn't really viable for many development efforts.

      --
      AJ Henderson
    23. Re:The cross-platform .NET? by UnknowingFool · · Score: 1

      Great and you promise that MS will never threaten legal action on anything developed in Mono. Has Ms made assurances of any kind? You haven't addressed that point.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    24. Re:The cross-platform .NET? by butalearner · · Score: 1

      As far as I recall it does a step further: there are still a few things in Mono that are not covered by (1) the ECMA standard, (2) Microsoft's promise, or (3) the Novell deal. ASP and ADO.NET for example, and I think Windows Forms. I entirely avoid C# so I forget the list, but I do remember that Microsoft offered no comment when asked about people using these specific parts. I thought, as the GP said, the Mono project was going to offer a minimal distribution that stripped out the offending parts, but it doesn't look like that ever happened.

    25. Re:The cross-platform .NET? by ByOhTek · · Score: 2

      Here are my reasons.

      (1) The API is very well document. Admittedly, Java and python are about as good. All three seem to have differences in where their documentation excel/lack, for me the .NET documentation seems a bit better.
      (2) Even considering Psycho, it is faster than Python, and depending on the task, the speed can go between slightly faster, parity and slightly slower than Java
      (3) Visual Studio is an excellent IDE, probably my favorite (but opinions vary). I just started using MonoDevelop, and it has now beaten out Eclipse as my #2 (this is simply rating IDEs for the languages they work best on, not all languages). Mind you, this is a personal preference, but there are plenty who will agree with it (and since someone will say so, plenty who will disagree as well). Java with a good IDE (Eclipse/Netbeans) comes close, but I've yet to see a good autocomlpeter for python, which makes sense given the language - that would be a non-trivial task.
      (4) I've had better luck in running .NET apps and running them on non-windows desktop platform, than Java apps running on multiple platforms. Mind you, to get this to work their are a few parts of the API you need to avoid, primarily WPF. Again I've seen opinions vary on this.
      (5) The .NET method for accessing native libraries is much easier/cleaner than that of Java or Python
      (6) Programming file IO seems a lot cleaner than you would get in the cluttered mess Java gives you. Python has .NET beat here, though.
      (7) Dynamically loading/unloading .NET libraries from .NET is easier than doing the same for Java libraries in Java. Again, I think Python has a slight advantage here.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    26. Re:The cross-platform .NET? by man_of_mr_e · · Score: 1

      Microsoft can threaten legal action on anything. Nothing special about Mono in that regard.

    27. Re:The cross-platform .NET? by ByOhTek · · Score: 1

      I'd argue that properties aren't that great. Unless I'm mistaken, they are function calls that can be assigned to (instead of putting the argument in parenthesis), that lack parenthesis.

      They are convenient, but they can cause problems as a novice developer may not realize they have function-like overhead. I can see a lot of good logic for not adding them to a language.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    28. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      Can you provide assurances that Microsoft will never threaten legal action on anything developed with GTK, Qt,. Java, glib, or whatever else?

      At this level of detail your point is totally silly -- saying that GTK# somehow has a significantly elevated risk because of Mono doesn't become true just because you wish so. Bring up a specific problem if you can, then we can start talking.

    29. Re:The cross-platform .NET? by TrueSatan · · Score: 1

      At one time De Icaza was a board member of the FSF and as such he was asked by the rest of the board to make the minimal distribution you mentioned...he agreed to do so and gave this agreement as a firm commitment to the rest of the board...he then reneged on this undertaking and that fact played a very large part in his removal from the board. Following on from this the FSF has encouraged the MONO developers to do the work necessary to produce this minimal distribution but to no avail.

    30. Re:The cross-platform .NET? by geggo98 · · Score: 1
      C# has some major advantages over other languages, namely:
      1. A very advanced type systems. I supports typed collections better than Java, being on par with C++. You can even formulate queries on a database, the filesystem, etc and the type system will make sure that everything fits together. This is all done without ugly "hacks" for special cases.
      2. Type inference.
        You can just write "var i=...". When the compiler compiles your code, it will find out the real type of "i" and replace "var" through that type. So it can typecheck your code, but you can just behave as if you were in a weakly typed script language.
      3. Closures and lambda expressions.
        You already know them from Python. You don't have them in Java.
      4. Delegates.
        These are funtion pointers done right. They are very handy for callbacks, e.g. for UI programming.
      5. A very good tool support.
        The language allows very deep static analysis. So it supports refactoring and statical error checking. Java has the similar features. Python is more limited regarding this.
      6. Support for generated code with partial classes
        You can define a class partial in source code and partial in compiled code. This allows a controlled mix of generated and hand written code without nasty hacks. Very handy for UI programming or in the enterprise where code generation is still the norm.
      7. Implementations are available for all major platforms (partially thanks to mono) and even for very limited devices (thanks to the open source .net micro framework).

      I am a Java/Scala developer. But from time to time I envy the .NET developers. Beside politics, C# could be the standard scription langauge for Unix, better than Perl or Bash. With Mono there is even a scripting frontend for C#.

    31. Re:The cross-platform .NET? by jjohnson · · Score: 1

      No, you can't just use MS's .NET. If you write C# for linux to run on Mono, you have to avoid the proprietary bits of the .NET platform and use swap-ins. This makes your code non-portable to MS's .NET, which lacks the swap-ins but includes the proprietary bits.

      In other words, thanks to the proprietary stuff, a Mono platform simply cannot be a complete implementation of .NET. When Novell had cut a deal with MS, it could be because it could include the proprietary parts, but since Novell shed Mono, you're back to a separate and incompatible library for the virtual machine.

      --
      Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
    32. Re:The cross-platform .NET? by gbjbaanb · · Score: 2

      In theory, .NET is the only language/runtime/framework/library you'll ever need, but in practice......

      in practice, you use different tools for different jobs. Line of Business apps are still being written in Java, more "hardcore" apps are still being written in C++, more webserver apps are being written in PHP. I think I like this state of affairs, because I wouldn't want to be tied into a single system forever. Apart from being a bit boring, you hit the reason right - it stagnates and never sees any need to compete.

      So Mono isn't helping, its trying to make the 'one system to rule them all' come about and we both agree here that that is a bad thing. If Miguel really wanted to improve the overall marketplace, he'd be writing dev tools that kicked ass for Linux/iOS/etc or creating a library platform for all the other languages out there - imagine the .NET framework that he has for Mono available as a native tool for C, PHP and Python code. That would be helping us out. Making a .NET on Linux really isn't.

      I do applaud the work he's done, and I applaud C# as a language (its not so bad at all), but I really think he's lost his way here, become too narrow-focussed on one thing.

    33. Re:The cross-platform .NET? by fbjon · · Score: 1

      I'd like to see an actual example of that being the case. I've never done anything with .Net myself, but from my (rather limited) personal experience, I haven't been able to get apps from the Windows side to run properly under Linux. I'm sure it's perfectly possible, but is it useful and/or workable? Is it still possible if Microsoft decides to stamp out competition?

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    34. Re:The cross-platform .NET? by Jason+Earl · · Score: 1

      How important are XBox Live Indie Games really? XBox is basically the second most popular gaming console, and is behind by a large margin. Microsoft's phone stuff is so far behind that even Nokia is not going to be able to save it.

      Besides, Mono doesn't help with either of these areas. If you want to develop for XBox Live or Microsoft's mobile OS you use Microsoft's tools, full stop. I suppose theoretically you could use Mono's non-free software to develop for iOS, Android, and Microsoft's platforms, but you would still have to learn three different APIs, and on the two most popular platforms (Android and iOS) you would have to use non-native tools.

      It seems to me that you'd have to *really* like C# to go through that hassle.

    35. Re:The cross-platform .NET? by man_of_mr_e · · Score: 1

      I'm not talking about taking Windows apps and running them on Linux, yes, that will need the proprietary stuff.

      I'm talking about building apps designed to run on all 3 major platforms that do not use the proprietary stack.

    36. Re:The cross-platform .NET? by oh_my_080980980 · · Score: 0

      You meant to say has Abstraction, which is Object Oriented language feature. But basically C# is a really bad Java knock off.

      You don't want to develop in C#, it's a pain in the ass.

    37. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      You can do the same thing in C++ by overloading the assignment operator.

    38. Re:The cross-platform .NET? by ByOhTek · · Score: 1

      You can reference arrays out of bounds in C without checking if the access is valid... Doesn't make it a good idea.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    39. Re:The cross-platform .NET? by Etrigoth · · Score: 1

      There are many ways around this, interfaces, strategy factory and repository patterns, he'll even dynamic keyword or il rewriting solutions a lá Jon skeet or even code weaving with AOP solutions.

      --
      When we remember we are all mad, the mysteries disappear and life stands explained.
    40. Re:The cross-platform .NET? by Etrigoth · · Score: 1

      As a .net implementation, Mono is actually very complete:
          http://www.mono-project.com/Compatibility

      Which are these essential parts of which you speak?

      --
      When we remember we are all mad, the mysteries disappear and life stands explained.
    41. Re:The cross-platform .NET? by ncc74656 · · Score: 1

      I've never done anything with .Net myself, but from my (rather limited) personal experience, I haven't been able to get apps from the Windows side to run properly under Linux.

      I've built some simple command-line apps in VS2008 and run the resulting binaries under Mono. I redid my website a while back with ASP.NET; it's served up by a Gentoo VPS running Apache and Mono. The menus it uses are generated by an off-the-shelf menu control. The only bits of weirdness I've run across so far have to do with database connectivity, and that's mainly due to VS2008 wanting to generate SQL code in the particular flavor that SQL Server uses; a few manual edits here and there will get it running with MySQL while maintaining compatibility with SQL Server.

      --
      20 January 2017: the End of an Error.
    42. Re:The cross-platform .NET? by shutdown+-p+now · · Score: 1

      So, my question is this, what is so great about C# that people seem willing to practically move heaven and earth to shoehorn it in to every platform they can get their hands on

      As a language, C# is significantly better than Java, feature-wise. Most notably you get proper closures (which can capture mutability of variables) with a very concise sequence with type inference - permitting to write many things as short as they would look in e.g. Ruby. There are many other neat things, but I think this one is most notable; if you want, I can go into more detail about what C# has that Java does not, and how it matters.

      On the other hand, you still retain static typing (which many people consider a benefit), and, since the bytecode is JIT-compiled, performance is significantly better than a straightforward bytecode interpreter such as CPython or Ruby.

    43. Re:The cross-platform .NET? by shutdown+-p+now · · Score: 1

      They are convenient, but they can cause problems as a novice developer may not realize they have function-like overhead.

      The burden falls on library authors to not provide properties which have significant overhead when setting (indeed, most style guides require to use Set-methods for anything that is not trivial).

      On the other hand, the existing convention in Java is not any better - since any field is wrapped into a pair of get/set methods for public consumption (so as to enforce encapsulation, and to allow to add advanced logic later), the caller still has no idea if the method call carries overhead, or is a trivial "return x;" type accessor (which would be inlined by JIT).

    44. Re:The cross-platform .NET? by shutdown+-p+now · · Score: 1

      The difference among most languages is just syntax, which is trivial.

      It's not, otherwise we'd still be coding in C. E.g. OOP is "just syntax" (see GObject), but it's a damn convenient one which matters a lot. Similarly closures/lambdas are "just syntax" (you can always write a closure class yourself and fill & pass it manually), but in practice they completely change how APIs are designed, making them better.

    45. Re:The cross-platform .NET? by shutdown+-p+now · · Score: 1

      Syntactically, C# is slightly closer to C++ than Java - base class initialization syntax, inheritance syntax, "bool" vs "boolean" etc (deliberately; according to Anders, they set off to design a language that people writing C++ on Win32 could migrate to more easily), but this is indeed largely superficial.

      However, one place where C# is decidedly not the same as Java, and much closer to C++ (or rather plain C) is where it has raw pointers and pointer arithmetic.

    46. Re:The cross-platform .NET? by shutdown+-p+now · · Score: 1

      I am a Java/Scala developer. But from time to time I envy the .NET developers.

      Coming from a Scala developer, that is strange. The only annoyance I can think of that Scala has and C#/.NET doesn't is non-reified generics with all that entails (inability to implement two interfaces different only in generic type parameters, inability to do an instanceof-check for a particular specialization of a generic, no support for "new T" or "new T[]" etc). It may be a big one, but Scala has many other features to compensate, IMO.

      Beside politics, C# could be the standard scription langauge for Unix,

      Why would you want a statically typed language as a scripting language?

    47. Re:The cross-platform .NET? by amliebsch · · Score: 1

      Has Ms made assurances of any kind?

      Yes.

      http://www.microsoft.com/interop/cp/default.mspx

      Note this does not cover their proprietary frameworks like Windows Forms or ASP.NET, but it is most of the framework.

      --
      If you don't know where you are going, you will wind up somewhere else.
    48. Re:The cross-platform .NET? by exomondo · · Score: 1

      How important are XBox Live Indie Games really?

      What sort of a question is that? If you'd had a look through the titles available you'd see they are very important for anyone wanting to start developing games or for any young game company.

      Microsoft's phone stuff is so far behind that even Nokia is not going to be able to save it.

      yes, any fledgling platform is going to start at the bottom.

      Besides, Mono doesn't help with either of these areas. If you want to develop for XBox Live or Microsoft's mobile OS you use Microsoft's tools, full stop.

      obviously, and mono isn't an attempt to change that.

      I suppose theoretically you could use Mono's non-free software to develop for iOS, Android, and Microsoft's platforms, but you would still have to learn three different APIs, and on the two most popular platforms (Android and iOS) you would have to use non-native tools.

      if you're using native features then you're going to need to use those different APIs but that's no different from doing it without Mono, the advantage is all of your common logic is exactly the same code.

      It seems to me that you'd have to *really* like C# to go through that hassle.

      hassle? the ability to write your logic code once and not having to change it when you port your application across platforms sounds like the opposite of a hassle to me.

    49. Re:The cross-platform .NET? by exomondo · · Score: 1

      Add to that there is the looming threat of MS legal action at any time.

      Oh come on, people have been saying that for nearly 7 years now, it's getting old. On top of that there's the community promise.

    50. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      They failed in their first attempt at making Mono a ubiquitous development platform

      Thats not the case, Mono is a "filler" for MS-DotNet on the linux market.
      As Novell had that nasty agreement with MS where the later promised to dont sue the former clients, you, as a client, get the posibility of running DotNet code on linux legally avoiding a MS lock-in.

      Novell wons, MS wons, we get the job done and thats it. Well, Novell loses too as its now clear.

      Also, never heard of anyone sane aiming directly for Mono, is always MS with Mono as a 'business strategy backup', but of course, I am limited to my experience here. But I have indeed used Mono on both Wintel and linux boxes on both Intel and PowerPC platforms, on every instance I can remember Wintel+MSDotNet clearly won on overall server performance and memory usage.

      Mono have several issues, for the incomplete API there are workarounds, but hardcoded thread limit (256!) and its incapacity to handle big heaps are particularly blockers for heavy-duty jobs.
      But hey! You would not be using DotNet for heavy-duty stuff anyway, right? right?

      Dont get me wrong here, Mono is fine, it works and does run DotNet on linux perfectly.
      Mono by itself is not necessary, any out-of-the-box reasonable efficient DotNet solution for linux would do, as long it is MS-sue free.

      The king is dead, long live the king!

    51. Re:The cross-platform .NET? by jjohnson · · Score: 1

      You're correct that there are ways to handle this situation, but having to do so rather voids the point about it being cross-platform, doesn't it?

      --
      Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
    52. Re:The cross-platform .NET? by tepples · · Score: 1

      hassle? the ability to write your logic code once and not having to change it when you port your application across platforms sounds like the opposite of a hassle to me.

      Someone else claims that sharing logic code between games that use very different kinds of input produces an end result that feels perfect on neither platform.

    53. Re:The cross-platform .NET? by exomondo · · Score: 1

      hassle? the ability to write your logic code once and not having to change it when you port your application across platforms sounds like the opposite of a hassle to me.

      Someone else claims that sharing logic code between games that use very different kinds of input produces an end result that feels perfect on neither platform.

      'Someone else' is doing it wrong.

    54. Re:The cross-platform .NET? by guruevi · · Score: 1

      Another problem with .NET/Mono is that Microsoft has historically never committed to a certain programming language and environment for more than a decade. Now it's .NET, before it was VB, they have had their own flavor of C and Java which gives major issues now 10 years later when you try to compile an obscure library with a non-Microsoft compiler or even a newer version of Visual Studio. We still have to purchase Visual C++ 6 to support a crappy library which won't compile in later versions (closed hardware, licensing and FDA validation issues don't allow us to rewrite it either).

      Even .NET is at version 4 as if it were a software package that is going to be outdated by version 5 with major backwards and forwards compatibility issues. .NET programs just can't be ported to another platform easily either since there is no fully ported .NET version for them except for Linux/Mac and the framework is just too big, interdependent and complicated to even port small portions of it to certain targets (SPARC, Power, ARM).

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    55. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      Mono has addressed the legal issues by seperating the Microsoft proprietary stuff from the ISO standard stuff, and supplying non-proprietary alternatives to several parts of the system..

      This is untrue. Mono is not separated in anyway whatsoever, not in the original sources, nor in packaging for distros.

      See, for example, Jo Shields' (who packages Mono for Debian and Ubuntu's) unedited response to this direct question: http://www.the-source.com/2010/12/on-mono-packaging/

      Miguel de Icaza's position is that Mono is covered under a trinity of protection: ECMA standards, Microsoft Covenants/Contributions, and Code-That-Simply-Isn't-Patented. Believe him or not, that's your own choice - but no one (save those who are mistaken or lying) asserts that Mono is somehow "split" into Microsoft/ISO bits.

      It just ain't so.

    56. Re:The cross-platform .NET? by Anonymous Coward · · Score: 0

      Thank you for being one of the few people to point out that back in the day the FSF was trying hard to work with Miguel de Icaza on producing a truly safe implementation of .NET, and that is was Miguel who couldn't be bothered to keep his word.

    57. Re:The cross-platform .NET? by man_of_mr_e · · Score: 1

      You're taking both my comments and Jo's out of context. Nothing that's in the core mono stuff is considered "scary" or "unsafe". Not all of it is in the standard, but there's a difference between "high risk" and "non-standard". The stuff that's high risk is seperated. The stuff that is highly unlikely to be legally risky is still included in the core.

      But, be that as it may, it's quite possible to simply strip out the contested namespaces with a few shell scripts. So that's not really a major issue. Whether or not Mono would still work is debateable, but in the case of such a situation it would be safe to say that other alternatives would get written quickly if that were the case.

    58. Re:The cross-platform .NET? by UnknowingFool · · Score: 1
      That list does not contain the .NET framework and gives MS an exception:

      This promise by Microsoft is not an assurance that either (i) any of Microsoft's issued patent claims covers a Covered Implementation or are enforceable, or (ii) a Covered Implementation would not infringe patents or other intellectual property rights of any third party. No other rights except those expressly stated in this promise shall be deemed granted, waived or received by implication, exhaustion, estoppel, or otherwise.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    59. Re:The cross-platform .NET? by UnknowingFool · · Score: 1

      The main difference in everything you listed is that they are developed completely independent of MS. Mono depends on the .NET framework. They also do not threaten MS in the same way. MS has a vested interest in maintaining the cross-platform capability of .NET only for their products. They really don't want to see it becoming cross platform to other platforms. They want developers using .NET for Windows, Xbox, WP7 not Linux, Android, etc.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    60. Re:The cross-platform .NET? by geggo98 · · Score: 1

      Coming from a Scala developer, that is strange. The only annoyance I can think of that Scala has and C#/.NET doesn't is non-reified generics with all that entails (inability to implement two interfaces different only in generic type parameters, inability to do an instanceof-check for a particular specialization of a generic, no support for "new T" or "new T[]" etc). It may be a big one, but Scala has many other features to compensate, IMO.

      Implicit classes are a nice feature. They are part of LINQ.

      Aditionally C# is the standard language of .NET, Scala is only a niche language on the Java paltform. So most .NET library support all the neat C# fatures. On the othe side only very few Java libraries have special Scala support. Of course you can still use them with Scala, but you have to abandon most Scala faeutres (e.g. closures).

      Why would you want a statically typed language as a scripting language?

      Because it's a statically typed language that can be used like a dynmically typed. You don't write types anywhere and the compiler adds them for you. So you will get type errors on compile time eithout having to write the types explicitely down.

    61. Re:The cross-platform .NET? by shutdown+-p+now · · Score: 1

      Because it's a statically typed language that can be used like a dynmically typed. You don't write types anywhere and the compiler adds them for you. So you will get type errors on compile time eithout having to write the types explicitely down.

      Well, type inference in C# only works on local variable declarations and in lambdas, and the two cannot be combined (i.e. you can't write "var f = x => x + 1"), so it's fairly limited. You still have to explicitly type method parameters, properties and fields.

      As well, this still isn't quite the same as dynamic typing. Much more extensive type inference can be seen in OCaml, where you can write a function like "let f x = x#foo", and it will actually infer the type of x as "some object having method foo" - and even that is not a perfect substitute for duck typing.

      Now C# actually does have true dynamic typing these days. Still, this is opt-in; for scripts, I think it is reasonable to have it by default.

    62. Re:The cross-platform .NET? by Jason+Earl · · Score: 1

      Thanks to the Mono people C# is essentially the only language that even pretends to be cross-platform to all of these devices. So I suppose I understand the theory, especially if you were writing the sort of game where the logic code comprised a major part of the project.

      Still, unless MonoDroid and MonoTouch are documented far better and come with far more examples than Mono itself, I can't see how choosing C# could possibly be a win. Let's face it. XBox Live Indie is a ghetto on the #2 console (that might well soon be #3). Financially you'd probably be better off just to ignore it completely. MonoDroid and MonoTouch would allow you to use C# on most of the major platforms for logic code, but they force you into using their wrappings for the native APIs for the UI code. Not only are you at the mercy of Novell for updates to these APIs (and they just fired all of their Mono developers), but you are essentially blazing your own trail. Very few developers are taking this path, and that means that *you* get to find all of the bugs. You could wait for Xamarin to save you, but they have to re-write the whole thing from scratch, and then try and re-sell developers on the idea that C# is what they really want (again). The mobile and game space is likely to be really different by the time Xamarin has something to sell. Who knows, by then perhaps Android (or iOS) will be the only platform that matters. If Microsoft really wants C# to stay relevant in this space then it *really* needs to do something quickly. Microsoft has the money to make things happen. Unfortunately, the execs at Microsoft have pinned their hopes on Nokia's first WinPhone being so awesome that people flock to their platform. That seems like a *very* long shot to me, but it probably is enough that it will keep Microsoft from funding Xamarin's work, which is the only thing that is likely to keep C# relevant in this segment of the computing world.

      From a practical standpoint, if you drop support for the XBox, you could write your core logic in C or C++ and use the native APIs for the UI on iOS and Android. I would bet that this is a far more popular choice than choosing C#. Most developers probably just write one app in Java, one in ObjC, and possibly one in C# if they really want to try their luck on the XBox, and call it good.

    63. Re:The cross-platform .NET? by exomondo · · Score: 1

      The benefit is that you aren't tied to just the mono apis, you can still use the native apis as well. this means you have a core logic written in c# that is portable across Windows, XBox, Linux, WP7, Android and iOS, then the only thing you have do is put in the necessary native calls on each platform, this obviously gives you a massive saving on maintenance.

    64. Re:The cross-platform .NET? by Flodis · · Score: 1

      I don't read it that way. I read it as:
      (i) An implementation doesn't necessarily have to use MS patents, and even if it does, those patents aren't necessarily enforceable.
      (ii) MS can't guarantee that an implementation doesn't infringe on third parties' claims.
      ... followed by some (standard?) legalese that the document only covers the things that the document actually covers.

      While writing this, I had to backtrack to find the legal document, and noticed your other posts about MONO. Are you just trolling?

  2. Give it a rest by Anonymous Coward · · Score: 0

    Go away. .NET has no business being on iOS

    1. Re:Give it a rest by tepples · · Score: 1
      Anonymous Coward wrote:

      .NET has no business being on iOS

      Then how do you recommend making one application whose business logic runs on Windows Phone 7 and iOS, or one video game whose game logic runs on both Xbox 360 and iOS? There's an old technique of splitting an application into a front-end and a back-end, allowing different presentation modules (input, graphics, etc.) for different platforms to share the same application logic. It has been called "I/O abstraction", "model-view-controller", or "multitier architecture", according to whatever fad is in season. But this that works only if all platforms share a language in which to write the application logic. All Windows Phone 7 applications and all Xbox 360 Indie Games must be written in a language that compiles to verifiably type-safe IL, which rules out standard C++ and Objective-C.

    2. Re:Give it a rest by spaceplanesfan · · Score: 0

      Thats is very different thing.
      Having mono to run windows apps aka wine is great thing, and in fact even patent matter doesn't matter.
      After all we use video codecs that breach all kinds of patents.

      What does matter is writing native Linux apps in mono.
      That is ugly, its like using wine to write Linux apps, and has unnecessary patent riscs (I don't really believe that mono infringes MS patents, but regardless of that MS could generate a ton of FUD if they claimed that it does)

      And this is the thing many Linux users including me don't like in mono.

    3. Re:Give it a rest by Anonymous Coward · · Score: 0

      Windows Phone 7

      What's that?

      one video game whose game logic runs on both Xbox 360 and iOS?

      When Microsoft releases a real .Net virtual machine for the iPhone and it gets accepted as an officially sanctioned target for development by Apple, then we can talk. Until then, I think I'll stick to Objective C where my code is first class and a development environment built by pros and not some hacked together shit put out by a bunch of unemployed amateurs.

    4. Re:Give it a rest by s73v3r · · Score: 1

      You bitch to Microsoft for not making that possible by not allowing native code.

    5. Re:Give it a rest by jellomizer · · Score: 1

      I would love it if .NET worked on Android and iOS, and Java Worked on iOS and Windows Mobile.
      Why should developer have to recode their application for every Mobile OS? They are already on tight controlled budget (Normally can't sell an app more then $10.00, and they will get $7.00 from that sales).

      This stuff about Open Source Purity really gets in the way of getting the job done, .NET will not go away any time soon. There are a lot of Apps and Business Logic out there in .NET that can probably be moved to mobile devices. Having to recode every time is harking back to the 1970's again. Developers and Customers should be Free of these hardware wars if they choose.
      You have closed platforms of iOS and Windows Mobile and a partially closed platform of Android. What ever you are doing isn't Pure anyways, so might as well get the job done if you can't follow your ideals.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:Give it a rest by aristotle-dude · · Score: 1

      Anonymous Coward wrote:

      .NET has no business being on iOS

      Then how do you recommend making one application whose business logic runs on Windows Phone 7 and iOS, or one video game whose game logic runs on both Xbox 360 and iOS? There's an old technique of splitting an application into a front-end and a back-end, allowing different presentation modules (input, graphics, etc.) for different platforms to share the same application logic. It has been called "I/O abstraction", "model-view-controller", or "multitier architecture", according to whatever fad is in season. But this that works only if all platforms share a language in which to write the application logic. All Windows Phone 7 applications and all Xbox 360 Indie Games must be written in a language that compiles to verifiably type-safe IL, which rules out standard C++ and Objective-C.

      Simple, don't bother with a Windows Phone 7 port. If MSFT cannot be bothered to support standard C++ for the core logic engine of games or apps then they have to be willing to not have apps ported to their platform. If they want to be a player then they have to be willing to compromise. Even Apple supports standard C++ in combination with Objective C.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    7. Re:Give it a rest by thetoadwarrior · · Score: 1

      By the logic then why not put objective C on the xbox and windows phone 7. There would be a bigger benefit by doing that as there are already many iOS apps made where as by using mono you need to start from scratch in most instances seeing how Windows Phone 7 apps are nearly non-existent. We keep getting told MS loves the homebrew people and the hackers so surely getting objective C onto the developer friendly MS devices will be easier than trying to work with 'Evil Steve's' device.

    8. Re:Give it a rest by tepples · · Score: 1

      By the logic then why not put objective C on the xbox and windows phone 7.

      Microsoft loves homebrew as long as it gets to lock people into using its tools on its platform.

    9. Re:Give it a rest by ByOhTek · · Score: 1

      The same could be said for Java or many other similar setups for linux-only apps.

      The point is cross platform.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    10. Re:Give it a rest by spaceplanesfan · · Score: 1

      Sure. But unlike java, mono can be targeted my Microsoft in a FUD campaign.
      I am not saying that mono does anything illegal.

      It like Apple using nokia's QT in their iPhone. Image the lawsuits....
      (Even though QT is free and isn't covered by any patents of course)

      Also note that .NET is developed and controlled by Microsoft,
      so we can't take it and make it fit Linux better.

      But sure if you absolutely insist on coding in .NET, mono is nice to be available.

      And yes I think that Linux apps should only be developed in native toolkits, GTK, QT or whatsoever.
      But thats just a recommendation.

    11. Re:Give it a rest by ByOhTek · · Score: 1

      I'm trying to decide if you're being serious, or sarcastic, showing how silly the anti-mono people are. Assuming the former.

      It can also be targeted by OSS zealots in a FUD campaign.
      In fact, unlike such a campaign by MS, it, in fact, already has been, and continues to be.
      So what?

      Groups making use of Java can be targeted by Oracle FUD. in fact, unlike Mono from MS, they have.

      As for being able to make it better or not, the Mono project has added GTK bindings, so your logic.
      So much for no improvement there. Maybe it's not a core part of the runtime, but they can always add things to their implementation, and they can always make compatibility libs to run on the MS implementation, if less efficiently.

      Hmm, wait, Java is controlled by Oracle, so the same issue is present there too, and like .NET/Mono, there are now Open source Java implementations.

      So again, aside from tasks which it is not intended (single platform development), and the owner of .NET is not actively harassing groups making implementations (full compatibility or related), how is Java different.

      Actually, given those standard, .NET/Mono is starting to look like a better alternative.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    12. Re:Give it a rest by Anonymous Coward · · Score: 0

      As a consumer, I see no reason why I should spend money on Apps written a programmer too lazy to code for the native environment. When I can easily find something that was.

    13. Re:Give it a rest by jellomizer · · Score: 1

      As a consumer you really shouldn't care, just as long as it does what you want at a performance that you are happy with. This has nothing about a programmer being too lazy. It is about having a unified code base for the application. The time saved having one code for multiple products means resources can be put into adding more features or improving the product, as well making more money per app so you can hire more resources. Vs. Getting an App made just for your phone and have it go into abandonware in a year because the company went out of business, besides there isn't anything saying the app made just for the device had a developer who wasn't lazy, they could be just as lazy and have an app with less features and performs much worse due to the lazy developer.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    14. Re:Give it a rest by exomondo · · Score: 1

      What does matter is writing native Linux apps in mono. That is ugly, its like using wine to write Linux apps

      how is it different any different from using say java?

      and has unnecessary patent riscs (I don't really believe that mono infringes MS patents, but regardless of that MS could generate a ton of FUD if they claimed that it does)

      see the CP regarding the .Net ECMA specs.

    15. Re:Give it a rest by Anonymous Coward · · Score: 0

      When Microsoft releases a real .Net virtual machine for the iPhone and it gets accepted as an officially sanctioned target for development by Apple

      yes, your lack of ability means you shouldn't touch anything not blessed by apple, you aren't capable of comprehending anything outside of that environment.

      Until then, I think I'll stick to Objective C where my code is first class and a development environment built by pros and not some hacked together shit put out by a bunch of unemployed amateurs.

      the same kind of 'unemployed amateurs' built the 'hacked together' foundation that your platform is built on, but as a fucking retard you of course wouldn't know that.

  3. Who didn't see this coming? by Barbara,+not+Barbie · · Score: 3, Interesting
    Q. Who didn't see this coming?
    A. Miguel.

    "Xamarin" - because "Ximian" was already taken.

    --
    Let's call it what it is, Anti-Social Media.
    1. Re:Who didn't see this coming? by Richard_at_work · · Score: 3, Insightful

      Ximian was a company founded by Miguel in 1999.

      And also, what has this got to do with Miguel "not seeing this coming"? The thing people were beating him over the head with was the theory that Microsoft would step in and sue people left, right and centre. This isn't that, this is Mono's supporting company failing of its own accord, it has nothing to do with the viability of Mono.

    2. Re:Who didn't see this coming? by Anonymous Coward · · Score: 0

      Truth be told, Microsoft hasn't needed to step in. A failing company isn't a threat. In fact, Miguel's silliness only brings value to Microsoft's table, as it fails to be anything else than free marketing.

  4. Good news? by nicholas22 · · Score: 5, Interesting

    This brings on the specter of legal action by Attachmate. While there has always been the thought that Mono could be sued by Microsoft, such as lawsuit would require Microsoft convincing a court that it was “just kidding” and the CLR/C# patent covenants are non-binding. Between their obligations to the ECMA standards body and the legal principal of equitable estoppel, the chance of this happening is slim to none. Attachmate is a completely different story. Even if they aren’t supporting it, they do own a product that is in direct competition with Xamarin’s future offerings. Without some sort of legal arrangement between Attachmate and Xamarin, the latter would face the daunting prospect of proving that their new development doesn’t use any the technology that the old one did. As a result of this, as well as the general uncertainty of any new product, some developers on the mono-android mailing list are stating that they are moving back to Java development for now. Source: http://www.infoq.com/news/2011/05/Mono-II

    1. Re:Good news? by Svartalf · · Score: 2

      If it's under the GPL and LGPL, it's going to be a rough case Attachmate would be making, considering that it's open licensed and they just kicked the team to the curb. Unless Attachmate has enforceable non-competes, along with carrying Mono forward, they're not going to have all that much of a case. Violating Copyright? Not really.

      As much as I wish that this stuff would have MS take the spectre of patent lawsuits away from this, or better yet, just die the death it needs to- this isn't a concern I have for it all.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    2. Re:Good news? by rantomaniac · · Score: 1

      If developers writing competing software having prior knowledge of [parts of] the code of the original was not a problem, the concept of clean room reverse engineering wouldn't exist.
      But since the Mono project used not to accept contributions from people that have seen Microsoft's shared source code, they are definitely aware of the danger and must be confident that a lawsuit from Attachmate isn't coming.

    3. Re:Good news? by nicholas22 · · Score: 1

      I don't think they will be GPL and LGPL? The MonoTouch and MonoDroid clones will be commercial offerings following a similar closed philosophy according to Miguel de Icaza (see www.tirania.org/blog)

    4. Re:Good news? by tepples · · Score: 1

      Then how can developers of free software (by the GNU definition) for the Android platform can afford $400 for Mono for Android plus $250 per year for updates? Or should developers of software for the Android platform just plan to ignore Windows Phone 7, Xbox 360, and other .NET-only platforms entirely?

    5. Re:Good news? by h4rr4r · · Score: 1

      That road goes both ways you know, maybe MS should start supporting dalvik.

    6. Re:Good news? by icebraining · · Score: 1

      By charging for the apps?

    7. Re:Good news? by s73v3r · · Score: 1

      Or should developers of software for the Android platform just plan to ignore Windows Phone 7

      Yes. It's not going anywhere.

    8. Re:Good news? by tepples · · Score: 1

      Or should developers of software for the Android platform just plan to ignore Windows Phone 7, Xbox 360 [...]?

      Yes. [Windows Phone 7 is] not going anywhere.

      Should developers also just plan to ignore Xbox 360?

    9. Re:Good news? by oakgrove · · Score: 1
      When Google or Microsoft ports .Net over to Android, I may consider developing in it. Otherwise, there is no way I'm going to use a second class dev environment on my first choice platform. Here is a list of the top grossing games on Android:
      • Paradise Island
      • Bakery Story
      • Restaurant Story
      • iMobsters
      • Homerun Battle 3D
      • Gun Brothers
      • World War

      What percentage of these games were written in mono?

      I don't have a list for ad supported stuff like Angry Birds but the Roveo people said they were planning to make a million dollars a month from it. I don't think AB is written in .Net.

      Despite what you say, the big money on Android does not appear to be in .Net so I think I'm making the right decision by sticking to Dalvik.

      --
      The soylentnews experiment has been a dismal failure.
    10. Re:Good news? by gbjbaanb · · Score: 1

      If I remember rightly, there was a patent agreement from Microsoft saying that they would not sue anyone patent-wise if they received Mono from Novell. The implication was that if you received itr from, RedHat say, then there was no agreement not to sue you.

      I don't know if that was transferred to Attachmate but I'm guessing that Xamarin doesn't have that agreement. I doubt Microsoft will do anything as getting more people hooked on .NET makes sense to them, but you never know - if Mono really takes off on iOS and Android and helps sell those phones instead of WP7, they might change their minds.

    11. Re:Good news? by exomondo · · Score: 1

      What percentage of these games were written in mono?

      I can see you're not one for innovation then. If the majority aren't doing it then you won't.

      Despite what you say, the big money on Android does not appear to be in .Net so I think I'm making the right decision by sticking to Dalvik.

      What are you on about? No end user even knows, much less cares if it's .Net or Dalvik, it makes no difference to them whatsoever.

    12. Re:Good news? by oakgrove · · Score: 1

      I can see you're not one for innovation then. If the majority aren't doing it then you won't.

      How is using a development environment that, at best, is a hack written and supported by unemployed amateurs "innovation"? The innovation is in the software I write and, I'm quite sure, I can write better software by sticking to the language officially sanctioned and proscribed by the developers of the operating system.

      What are you on about? No end user even knows, much less cares if it's .Net or Dalvik, it makes no difference to them whatsoever.

      I didn't say anything about what end users care about. I said the big money apps are all written sans mono. I'm here to get paid, not piddle around with some hack second class crap. I'll be more than happy to watch you do that. More money and users for me.

      --
      The soylentnews experiment has been a dismal failure.
    13. Re:Good news? by exomondo · · Score: 1

      I can see you're not one for innovation then. If the majority aren't doing it then you won't.

      How is using a development environment that, at best, is a hack written and supported by unemployed amateurs "innovation"? The innovation is in the software I write and, I'm quite sure, I can write better software by sticking to the language officially sanctioned and proscribed by the developers of the operating system.

      Clearly you are only interested in what others are doing rather than the merits of the framework. Linux was initially developed - and continues to be developed - by unemployed amateurs too and look at how well that is going. Innovation is about not just doing what everyone else is doing. Quite obviously you've never used Mono and since most people aren't using it you're not going to try it.

      What are you on about? No end user even knows, much less cares if it's .Net or Dalvik, it makes no difference to them whatsoever.

      I didn't say anything about what end users care about. I said the big money apps are all written sans mono. I'm here to get paid, not piddle around with some hack second class crap. I'll be more than happy to watch you do that. More money and users for me.

      clearly that's what you are implying given you seem to think that the 'big money', which comes from the end users (and advertisers), depends on the framework, which they know nothing about and has absolutely no impact on it whatsoever.

    14. Re:Good news? by oakgrove · · Score: 1

      Linux was initially developed - and continues to be developed - by unemployed amateurs too

      Yeah, I know right? Except, it's not. According to that credible report, 80 percent of the kernel comes to us via paid development. And why do you care anyway? The development environment for your precious monodroid doesn't run on Linux anyway.

      clearly that's what you are implying given you seem to think that the 'big money', which comes from the end users (and advertisers), depends on the framework, which they know nothing about and has absolutely no impact on it whatsoever.

      I'm not implying anything. I'll come out and say it. You cannot write apps in monodroid that are as good as apps that can be written in the real development kit nor can you write them as quickly. First of all, all of the developer documentation is written assuming java and Eclipse so you are hamstrung out of the gate using anything else. Secondly, for RAD, there is no drag and drop gui designer for monodroid, There are no tablet specific api's on monodroid so you are always going to be a step behind other developers. Worst of all, there is a performance penalty so by definition, there are some applications that can be written using java that will be too slow to deploy to users on monodroid. It's bad enough developing within the constraints of a mobile device in the first place, do you actually think I'm going to gimp it even more? Get real. At this point, I have to assume you monodroid people are all trolls out to confuse the development situation on Android to the benefit of competing platforms.

      --
      The soylentnews experiment has been a dismal failure.
    15. Re:Good news? by exomondo · · Score: 1

      Yeah, I know right? Except, it's not. According to that credible report, 80 percent of the kernel comes to us via paid development.

      So there's 20% of unemployed amateurs...better abandon the platform.

      The development environment for your precious monodroid doesn't run on Linux anyway.

      my precious monodroid? I have no involvement in the project and i don't even own an android device.

      I'll come out and say it. I cannot write apps in monodroid that are as good as apps that can be written in the real development kit nor can I write them as quickly.

      FTFY, don't project your inadequacies onto everyone else.

      First of all, all of the developer documentation is written assuming java and Eclipse so you are hamstrung out of the gate using anything else.

      So if you know C# and have developed functionality already you don't need to learn those java/eclipse aspects, you can leverage existing knowledge.

      There are no tablet specific api's on monodroid so you are always going to be a step behind other developers.

      Tablet-specific APIs? What is it you need that you seem incapable of doing with scalable code? or is it that you aren't/can't do scalable code?

      Worst of all, there is a performance penalty so by definition, there are some applications that can be written using java that will be too slow to deploy to users on monodroid.

      It's not the be-all and end-all of frameworks, you don't have to choose between mono or native. It's the same thing we have been doing in software development for ever, you choose the best tool for the specific job.

      It's bad enough developing within the constraints of a mobile device in the first place

      Welcome to software development, since you're new here you should learn to appreciate that the constraints of modern mobile development are actually quite relaxed and that those of us who have been in the field for a while find this to be extremely easy.

      At this point, I have to assume you monodroid people are all trolls out to confuse the development situation on Android to the benefit of competing platforms.

      And of course you assume wrong. I'm not a monodroid developer, but i have tried and can see the benefit in it if i were to develop and application that leverages that advantage.

    16. Re:Good news? by oakgrove · · Score: 1

      FTFY, don't project your inadequacies onto everyone else.

      Are you slow? Do I need to draw you a picture? Here, I'll quote myself. Read it out loud if you need to.

      First of all, all of the developer documentation is written assuming java and Eclipse so you are hamstrung out of the gate using anything else. Secondly, for RAD, there is no drag and drop gui designer for monodroid, There are no tablet specific api's on monodroid so you are always going to be a step behind other developers. Worst of all, there is a performance penalty so by definition, there are some applications that can be written using java that will be too slow to deploy to users on monodroid.

      Monodroid is not as advanced as the Java kit for android development. That is a monodroid inadequacy.

      First of all, all of the developer documentation is written assuming java and Eclipse so you are hamstrung out of the gate using anything else.

      So if you know C# and have developed functionality already you don't need to learn those java/eclipse aspects, you can leverage existing knowledge.

      You imply that you have mobile development experience. Now, I doubt it. The mere fact of knowing the language does not make you an Android developer, be it C# or Java. You have to be familiar with the apis, the app lifecycle, the idiosyncracies of the platform. Best practices. All of that and more is documented in excruciating detail at http://www.developer.android.com/ and it assumes java. You don't get that for mono.

      Tablet-specific APIs? What is it you need that you seem incapable of doing with scalable code? or is it that you aren't/can't do scalable code?

      Really? And here's more. None of that is available with monodroid.

      Welcome to software development, since you're new here

      What's that you were saying about projection?

      --
      The soylentnews experiment has been a dismal failure.
    17. Re:Good news? by exomondo · · Score: 1

      FTFY, don't project your inadequacies onto everyone else.

      Are you slow? Do I need to draw you a picture? Here, I'll quote myself. Read it out loud if you need to.

      I quite clearly refuted that point by point already. Re-quoting yourself just shows that you weren't able to comprehend what I wrote and therefore were unable to rebut it.

      Monodroid is not as advanced as the Java kit for android development. That is a monodroid inadequacy.

      'advanced' depends on what you're doing with it, and the fact that you can use both together means having mono is advantageous.

      You imply that you have mobile development experience. Now, I doubt it. The mere fact of knowing the language does not make you an Android developer, be it C# or Java.

      And i never said it did - don't make up rubbish like that - your inability to read and comprehend what was actually written leads you to that conclusion. I said you don't need to bother with those specific aspects if you've already learned them in a compatible framework, and that is absolutely correct. Or do you not understand the concept of code-reuse?

      You have to be familiar with the apis, the app lifecycle, the idiosyncracies of the platform. Best practices. All of that and more is documented in excruciating detail at http://www.developer.android.com/ and it assumes java. You don't get that for mono.

      Obviously using Mono doesn't mean you don't have to learn some platform-specific aspects, and no-one ever claimed that it did.

      Really? And here's more. None of that is available with monodroid.

      Those aren't tablet-specific, tablet is a form-factor, just as the 7" Galaxy tab is a tablet and doesn't need those APIs. Moreover if there is something unavailable in mono you can use the existing native implementation, but then that would be clear to you if you'd actually used mono.

      Welcome to software development, since you're new here

      What's that you were saying about projection?

      your willingness to evaluate a platform you've never used and complain about the constraints of modern mobile devices shows what i wrote is correct.

    18. Re:Good news? by oakgrove · · Score: 1

      I quite clearly refuted that point by point already. Re-quoting yourself just shows that you weren't able to comprehend what I wrote and therefore were unable to rebut it.

      What are you talking about? You didn't refute anything. You responded to me pointing out that the documentation is better for java android development than for mono on android by talking about code reuse in C# as if that had anything to do with what I was saying. Code reuse doesn't help you with the platform specific api's and idiosyncracies like application lifecycle, bugs, etc. which are all explained and laid out for java.

      Obviously using Mono doesn't mean you don't have to learn some platform-specific aspects, and no-one ever claimed that it did.

      Exactly and the support and documentation for that on the java side is much more mature.

      Those aren't tablet-specific, tablet is a form-factor, just as the 7" Galaxy tab is a tablet and doesn't need those APIs. Moreover if there is something unavailable in mono you can use the existing native implementation, but then that would be clear to you if you'd actually used mono.

      The last refuge of someone who is backed into a corner and just arguing for the sake of it is to start throwing out technicalities. You know just as well as I do that I we referring to API levels 11 and 12, i.e., Honeycomb 3.0 and 3.1. Neither of which are available for monodroid. So, just like mono in the desktop world, mobile mono will always be behind. For a developer, watching the cool kids do cool stuff while you are stuck with second rate limited crap is no fun.

      your willingness to evaluate a platform you've never used and complain about the constraints of modern mobile devices shows what i wrote is correct.

      I did evaluate it and I found it lacking.

      --
      The soylentnews experiment has been a dismal failure.
    19. Re:Good news? by exomondo · · Score: 1

      What are you talking about? You didn't refute anything.

      I clearly refuted it point by point.

      Code reuse doesn't help you with the platform specific api's and idiosyncracies like application lifecycle, bugs, etc. which are all explained and laid out for java.

      Of course it does, that code is NOT platform-specific, which is the whole point of mono, how can you not know that? you claim to have evaluated it but you don't know this most basic fact about it?

      Obviously using Mono doesn't mean you don't have to learn some platform-specific aspects, and no-one ever claimed that it did.

      Exactly and the support and documentation for that on the java side is much more mature.

      If you already know a supported .Net language then you don't need that particular documentation.

      The last refuge of someone who is backed into a corner and just arguing for the sake of it is to start throwing out technicalities. You know just as well as I do that I we referring to API levels 11 and 12, i.e., Honeycomb 3.0 and 3.1. Neither of which are available for monodroid.

      Obviously the point, that you seem to consistently miss, is that you don't need them to be. You write the platform specific stuff for the specific platform and leave the agnostic stuff in an agnostic language/platform, which - as you keep ignoring - is a benefit of mono.

      So, just like mono in the desktop world, mobile mono will always be behind. For a developer, watching the cool kids do cool stuff while you are stuck with second rate limited crap is no fun.

      Are you still incapable of grasping the simple fact - that would be obvious to you if you knew anything about mono - that you are not limited by using mono and that you can still use any and all of the existing native functionality when necessary?

      I did evaluate it and I found it lacking.

      how exactly did you evaluate it?

    20. Re:Good news? by Anonymous Coward · · Score: 0

      MonoTouch and MonoDroid are not and have never been Open Source of any kind. The competing alternatives that Ximian2 is developing will not be Open Source, either - according to Miguel's own blog.

      I guess some fired employees may be able to simply "re-implement" the exact product they were developing for the company that just let them go, but I also guess that company may decide they don't want that to happen - especially as the original company is still selling the product.

      For all we know, Attachmate may have had a set of plans for MonoTouch/MonoDroid that Miguel didn't like, and he took it as a opportunity to found a competing startup.

      I'm not saying that's what happened, but I will say if I was a corporate lawyer, I'd bet you a shiny new Rolex I could make a jury believe it.

    21. Re:Good news? by Flodis · · Score: 1

      Should developers also just plan to ignore Xbox 360?

      At least during work hours.

  5. I wonder if Apple would allow it... by mlts · · Score: 2

    Doesn't Apple have a prohibition of using a framework other than Objective C for their iOS apps? I know some tools get around this by making Objective C source code.

    1. Re:I wonder if Apple would allow it... by tepples · · Score: 4, Insightful

      Doesn't Apple have a prohibition of using a framework other than Objective C for their iOS apps?

      Apple has since rescinded this provision, apparently because it was causing Apple to lose money as games and other popular iOS apps that use internal scripting engines were getting kicked off the App Store.

    2. Re:I wonder if Apple would allow it... by kervin · · Score: 4, Interesting

      More likely because DOJ was beginning to probe on the behalf of Adobe.

    3. Re:I wonder if Apple would allow it... by Anonymous Coward · · Score: 0

      not anymore

    4. Re:I wonder if Apple would allow it... by Anonymous Coward · · Score: 0

      Objective C is not a framework.

    5. Re:I wonder if Apple would allow it... by UnknowingFool · · Score: 1

      Technically Objective C is a language and Apple allowed coding in C as Objective C is a superset of C. The framework was iOS and as other noted, there are exceptions allowed as long as you adhere to the guidelines.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    6. Re:I wonder if Apple would allow it... by aristotle-dude · · Score: 1

      Objective C is not a framework.

      You are right, the iOS SDK has frameworks in it which are based on the frameworks in OS X.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    7. Re:I wonder if Apple would allow it... by Anonymous Coward · · Score: 0

      The restrictions were loosened, but never applied to MonoTouch. They were about scripting libraries that access the device though wonky third party apis, instead of the official apple SDK way. Choice of Obj-C was never forced, you've always been welcome to compile your C or C++, or whatever else will spit out an ARM binary.

      MonoTouch compiles to native code and uses Apples native APIs the way they were meant to. There have been monotouch apps on the store for a long time, long before they loosened up the "no interpreted code" rules -- because there is no interpreted code in a monotouch app. Its your C# compiled natively, with the runtime linked in as a static library.

    8. Re:I wonder if Apple would allow it... by Anonymous Coward · · Score: 0

      I hadn't heard about this. Do you have any supporting links? I couldn't find any just last week, and this would ease my work A LOT.

    9. Re:I wonder if Apple would allow it... by tepples · · Score: 1

      Apple's ban on languages other than Objective-C and standard C++ ended in early September 2010, according to an Adobe press release.

  6. There are those who would say... by Anonymous Coward · · Score: 5, Insightful

    ...that the submitter should just state his opinion rather than hiding behind weasel words.

  7. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  8. IL to JSLINUX ? by Anonymous Coward · · Score: 0

    Are they gonna make IL2CPU and IL2JSLINUX: http://bellard.org/jslinux/

    Mono, winforms, gtk, xaml, etc, all in a browser. Or even the web-server in a browser for embedded unix.

  9. demise of open source ".NET-ness", a good thing? by CodeShark · · Score: 1

    Given that there is nothing MS would have liked to do more than to shut down Novell for ANY reason whatsoever, why would people consider the demise of ".NET" ness that is clearly open source and in many ways immune to patent litigation (although possibly not DMCA reverse engineering litigation -- I've heard that folks thought that was a possibility at one time) a good thing?

    That would be like saying that SCO's lawsuits had merit for including major Linux distributions in it's target scope, would it not? And I don't think Miguel et. al are so stupid as to put themselves blindly as targets in microsoft's corporate crosshairs, do you?

    --
    ...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
  10. from the point of view of getting things done by circletimessquare · · Score: 3, Insightful

    it's not a good thing that Mono should go away

    it is a good thing from the point of view of ideology, however

    but as a working programmer, i like getting things done. to hell with the ideologues

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:from the point of view of getting things done by Anonymous Coward · · Score: 0

      it's not a good thing that Mono should go away

      it is a good thing from the point of view of ideology, however

      but as a working programmer, i like getting things done. to hell with the ideologues

      As a consumer, I would prefer to not be at the mercy of one entity when I need to get something fixed or improved.

      To hell with your expedience. The end doesn't justify the means.

    2. Re:from the point of view of getting things done by circletimessquare · · Score: 0

      you're a pretty rare consumer, because consumers like uniformity

      but i will remember your words the next time i build a computer. i will not take solace in one SATA standard or one hard drive size. i will consider myself "at the mercy" of one oppressive uniform standard, and i will prefer to have my disk drives all sorts of random custom sizes and all SATA interfaces to be various and unique handcrafted cables with rare port shapes

      because i don't like expedience. i like to expend 10x the amount of grief and time build a new PC. because, you see, the ends of making the process easy and quick does not justify the means

      right?

      pffffffffffffffft. what an idiot

      --
      intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    3. Re:from the point of view of getting things done by icebraining · · Score: 1

      Parent said entity, not standard. The whole point of having a standard is to be able to have more than one entity provide a compatible device.

    4. Re:from the point of view of getting things done by Anonymous Coward · · Score: 0

      How is this any different from anything released on iOS or Windows or Mac or pretty much any commercial proprietary platform at any level of abstraction.

    5. Re:from the point of view of getting things done by circletimessquare · · Score: 1

      you mean a separate entity like mono?

      --
      intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    6. Re:from the point of view of getting things done by Anonymous Coward · · Score: 0

      Your first impression was correct, it is a good idea for Mono to go away, or perhaps you forgot the three Es of M$: Embrace, Extend, Extinguish.

    7. Re:from the point of view of getting things done by genghisjahn · · Score: 1

      I can't stress how great is is to write a application from Win 7 using Visual Studio 2010 and target the mono framework and then copy those files over to a Linux PC and or Mac with zero code changes and it all still works. I've done this. It's awesome. I don't think C# is the end all be all language to nkow. I'm loving what I'm learning with RoR and Python and I can't wait to use those platforms more...but Mono is greatness. That's my objective opinion.

      --
      Sorry about the mess.
    8. Re:from the point of view of getting things done by circletimessquare · · Score: 1

      the borg eyewear on the bill gates icon is a joke, not something to take as a realistic observation. you also might have noticed it is 2011, and google and apple are eating microsoft's lunch. in such a business environment, extending .NET use works to microsoft's advantage, and not something they want to discourage

      please get your mind out of 1996. thanks

      --
      intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    9. Re:from the point of view of getting things done by LWATCDR · · Score: 1

      Then stop being a consumer and start being a developer. I have never worked with Mono as a developer but some of the FOSS programs that where written with it are very useful. Since they are FOSS I can fix and modify them if I wish. But if you do not like them it is your right to not use them. You just have no right to crab about other choices since they do not really effect your freedom to write what you want.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    10. Re:from the point of view of getting things done by Anonymous Coward · · Score: 0

      Yes one of the great things about .NET is that its extremely useful if you are interested in SOLVING PROBLEMS IN EXCHANGE FOR MONEY. The rest of it is just entertainment for the academics and "spectators".

    11. Re:from the point of view of getting things done by Anonymous Coward · · Score: 0

      Do you use Mono? Does your software work under Mono?

    12. Re:from the point of view of getting things done by lgw · · Score: 1

      While I have given up all hope that you will learn to operate the shift key, could you at least refrain from starting a sentence in the subject line and finishing it in the post proper? I hope for your sake that you hire someone else to write your resume/linkedin.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    13. Re:from the point of view of getting things done by vajorie · · Score: 1

      but as a working programmer, i like getting things done. to hell with the ideologues

      I like how your signature contradicts your above argument :)

      intellectual property law is philosophically incoherent. it is your moral duty to ignore it

    14. Re:from the point of view of getting things done by Just+Some+Guy · · Score: 1

      The point of view of the ideologues is that they want it to remain legal for you to get things done. What assholes.

      --
      Dewey, what part of this looks like authorities should be involved?
    15. Re:from the point of view of getting things done by Anonymous Coward · · Score: 0

      No ideologues - no philosophy.
      No philosophy - no society.
      No society - no programmers.

    16. Re:from the point of view of getting things done by gbjbaanb · · Score: 1

      really? well, consider this:

      I've built PCs with SCSI, IDE, EIDE, SATA, eSATA, FC and iSCSI standards. And Thank god for them. See, if we didn't have all these things, you'd be building your next PC using an old ATA-33 connector and cable.

      The point of different standards like this is progress. Things get made better because better things come about.

      Consumers don't like uniformity anyway, they like the latest and greatest. They don't care about most standards, they care about throwing the old out and buying new stuff.

    17. Re:from the point of view of getting things done by jedidiah · · Score: 1

      Mono never really provided me any benefit as an actual end user.

      An ideological objection to Mono simply isn't required.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  11. Surely... by Richard_at_work · · Score: 4, Insightful

    these recent events might be the beginning of the demise of widespread use of Mono and other .NETiness in open source software, a good thing

    Surely thats a matter of opinion?

    1. Re:Surely... by neonux · · Score: 1

      You must be new here.

      --
      @neonux
    2. Re:Surely... by PsychicX · · Score: 4, Insightful

      It's a matter of unnecessary Slashdot editorializing, promotion of stupid viewpoints by stupid people. Free Software, amongst other things, exists to promote choice amongst developers and users both. So why is losing effective development choices productive? It isn't. But because there's a vague connection to Microsoft here, it must be evil and be destroyed. Especially now with Java in Oracle hands, what does this accomplish? It's like these people never got out of college and think their professors' dedication to C and a UNIX variant is the only legitimate viewpoint.

    3. Re:Surely... by Anonymous Coward · · Score: 0

      No, it's objective, cold, hard, truth...and don't call me Shirley.....

    4. Re:Surely... by Anonymous Coward · · Score: 0

      You must be new here.

      Came to say that.

      10 years ago, I called Miguel De Icaza a sellout.

      Sadly, it's been proven true.

    5. Re:Surely... by Anonymous Coward · · Score: 4, Insightful

      But because there's a vague connection to Microsoft here, it must be evil and be destroyed.

      First of all, it's not a "vague" connection between .NET and Microsoft, they created and own the platform FFS. The connection is as explicit as can be.

      Second, Microsoft has proven time and time again that given half a chance will fuck over anything and anybody that stands in their way. And has never stopped trying to take out FOSS, GPL, Linux, open standards and, again, pretty much anything they see as threatening their cosy monopolies. As we speak they're mounting another covert attack on Linux using software patents.

      Fool me once, shame on you, fool me twice, shame on me. Trust Microsoft? Sorry, never again.

    6. Re:Surely... by sqldr · · Score: 0

      Surely thats a matter of opinion

      No, this is slashdot. Anything made by or used by microsoft, no matter how well designed or useful, or open, is inherently evil and should be avoided, even at the expense of being completely irrational. You'll just have to use perl. Sorry.

      --
      I wrote my first program at the age of six, and I still can't work out how this website works.
    7. Re:Surely... by npsimons · · Score: 1, Troll

      these recent events might be the beginning of the demise of widespread use of Mono and other .NETiness in open source software, a good thing

      Surely thats a matter of opinion?

      Please cite, specifically, what Mono or C# brings to open source platforms that aren't already there and done better. There's nothing new in C#, and the JVM is already taking off with new programming languages, plus it's finally fast enough for most everything. Don't get me wrong, I'm glad that C# is exposing programmers to advanced language features, but these features have already existed in other programming languages for decades. Add to that the threat of patent violation lawsuits (which are *not* protected in OSS by MS's RAND licensing, no matter how loudly the fanbois scream), and you have a non-starter when it comes to Mono and C#. People don't trust Microsoft, and with good reason.

      I myself have avoided C# as a heavy software engineer, partly because I'm already pretty good at C and C++ (which C# will not replace in my field, embedded and OS), but also because I'd rather dabble in more interesting and truly free programming languges, such as Scala, Clojure, Haskell, OCaml, and Go. Not to mention that economically speaking, Mono and C# don't run on Android or iPhone (and I'm sure someone will point out some project or software shop trying to push their C# for Android/iPhone package, but I doubt the efficacy of those solutions).

    8. Re:Surely... by cyber-vandal · · Score: 2, Insightful

      People's lack of trust in Microsoft's behaviour is not some paranoid delusion but the result of years of experience of watching them misbehave. How do you know that Microsoft won't try to say that Mono violates their patents? They've already said that Linux does, but in the case of Mono they may well be able to prove it. I work in C# .NET and I really enjoy my job but I wouldn't trust Microsoft not to shit on a competitor. Even a brief look at their long and chequered legal history would show that.

    9. Re:Surely... by Anonymous Coward · · Score: 0

      If you really feel this way, then you're going to be really surprised to find out who one of the angel investors is.

    10. Re:Surely... by Anonymous Coward · · Score: 0

      FUD. Thanks for providing quite the complete and perfect example of fear, uncertainty, and doubt.

    11. Re:Surely... by PipsqueakOnAP133 · · Score: 1

      And compared to the monopoly days of yore, MS has gone downhill from there. Quite far downhill.

      I'd say that MS has an actual legitimate business need for gaining trust amongst customers and developers or else they're totally fucked.
      There's no reason not to take them at face value now (but always have an abandonment plan given their past) given that it is now in their best interest to not fuck customers and developers over.

      The alternative is that those FLOSS-supporters become exactly what they fought against: dictators and control-freaks telling people what they can or cannot do.

  12. I don't get it by pak9rabid · · Score: 1, Insightful

    Most companies won't touch it...if they're running on Linux, they're going to go with a language that's native to the platform, like Java. If you're a home user, most relevant software written in .NET isn't going to work with it. This just seems like an extremely futile attempt. Is Miguel hoping that one day Microsoft will say "hey, we really like what you've been doing...come work for us!"?

    1. Re:I don't get it by nicholas22 · · Score: 3, Interesting

      Java isn't native to Linux. But I get what you were trying to say.

    2. Re:I don't get it by Anonymous Coward · · Score: 0

      How is Java native to the Linux platform?

    3. Re:I don't get it by tepples · · Score: 1

      if they're running on Linux, they're going to go with a language that's native to the platform, like Java.

      Say a company wants to make an application available to the public, and the public owns a mix of iOS, Android, and Windows Phone 7 devices. But the developers don't want to perform a complete, error-introducing rewrite of the application logic when porting the application to another platform. So they have to write the application logic* in a language that iOS, Android, and Windows Phone 7 devices can all run. The only ones I can think of are C# and other languages that compile to verifiably type-safe IL.

      * Not including the front end, which will differ substantially per platform.

    4. Re:I don't get it by westlake · · Score: 2

      Most companies won't touch it...if they're running on Linux, they're going to go with a language that's native to the platform, like Java.

      What maks JAVA any more "natively" Linux than .NET or Mono?

    5. Re:I don't get it by pak9rabid · · Score: 1

      The fact that there's a fully supported jvm for it that isn't constantly trying to play catch-up with the upstream vendor.

    6. Re:I don't get it by Anonymous Coward · · Score: 0

      Companies already do that everyday by targeting WebKit, and deploy with containers like PhoneGap.
      Moving from WebKit to C# would be a really dumb move.

    7. Re:I don't get it by pak9rabid · · Score: 1

      That company would be best advised to bite the bullet and implement it 3 times...using the correct and supported languages for the targeted platform...that is if they enjoy staying in business.

    8. Re:I don't get it by pak9rabid · · Score: 1

      By native, I mean there's a fully supported jvm available for it that isn't currently trying to play catchup with an upstream vendor.

    9. Re:I don't get it by Anonymous Coward · · Score: 0

      By that definition, Flash is native on Linux too?

    10. Re:I don't get it by Anonymous Coward · · Score: 0

      because tripling your development costs is an excellent way to stay in business!

    11. Re:I don't get it by Anonymous Coward · · Score: 0

      Ugh, for crying out loud, Mono isn't playing catch up. They supported 4.0 before Microsoft even did.

    12. Re:I don't get it by Anonymous Coward · · Score: 0

      Java also generates native linux executable code.

      How is Java for Linux not native to Linux? Do you mean historically or?

    13. Re:I don't get it by Locutus · · Score: 1

      one problem I see is that Microsoft is well known for locking its developers onto their platform. This is a well known business method used on the Windows OS. Given that, why would you want to fall for using the platform they control( MS .Net) to create applications for the 2 dominant phone platforms, iOS and Android, so you can get the also-ran Windows Phone 7 and be subject to losing iOS and Android at Microsoft's whim?

      For crying out loud, Microsoft created their .Net stuff to thwart Java because Java was cross platform. "Does anyone remember Windows" was what Bill Gates exclaimed at an internal Microsoft meeting as the development discussions on where to take Java on Windows became a heated discussion on making a better Java than others. The result of that meeting was stoppage of all current Microsoft Java projects and the beginning of binding MS Java to Windows and breaking the cross platform nature and license of Java. It was also the beginning of their attack on Borland, one of the leading language and Java tools shops at the time, and the beginning of Microsoft's Java-like platform called MS .Net.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    14. Re:I don't get it by greap · · Score: 3, Informative

      The bits that make sense in cross platform systems have been done: http://www.mono-project.com/Compatibility

      Those that are missing currently (almost entirely limited to entity framework and workflow) have open source alternatives already available (EG NHibernate for EF).

      In terms of release cycles it varies fairly wildly. Mono actually was at release for several parts of Framework 4 before Microsoft had their version out of the door, Microsoft tend to be fairly verbose with the roadmap and also put out a great deal of CTP’s targeting small sections of functionality which allows downstream projects to stay on top of what’s coming,

    15. Re:I don't get it by BRSloth · · Score: 1

      Not sure what you mean "native to the platform, like Java". Java is mostly platform-less (more or less) as most code can run unmodified in any platform, be it Linux, OS X or Windows (again, let me say "more or less". There are some differences between platforms, even in Java).

      Also, most Linux home users already run Mono applications, like Banshee and Tomboy, which are part of the GNOME desktop.

      That being said, in my opinion the biggest problem with Mono (apart from the whole patent debacle) is that it was always lagging behind the official .NET specification. I lost the count of the number of .NET applications, compiled in the official C# compiler, that I tried to run with it and it would simply not work.

    16. Re:I don't get it by Anonymous Coward · · Score: 0

      So, basically you are redefining the word 'native'.

    17. Re:I don't get it by Anonymous Coward · · Score: 0

      Yes most companies will just run a Microsoft stack for .NET apps... But if they then want to write an iPhone or Android app to go along with that then mono is an excellent choice.

      Personally I like being able to choose the language that best fits the job, and mono is the only one that lets me write C#, java J#, python, and even VB in the same application.

    18. Re:I don't get it by Anonymous Coward · · Score: 0

      How are the GUI libraries?

    19. Re:I don't get it by kaffiene · · Score: 1

      You can get it under the GPL licence?

  13. Re:demise of open source ".NET-ness", a good thing by Anonymous Coward · · Score: 0

    Given that there is nothing MS would have liked to do more than to shut down Novell for ANY reason whatsoever....

    Your premise is wrong. It's been a long time since Novell was a significant Microsoft competitor.

  14. Microsoft is his friend by Anonymous Coward · · Score: 1

    To the extent that Microsoft is anyone's friend, it is his friend. He has had such a relationship with Microsoft even before Mono. Personally, I always thought he was some kind of Microsoft mole in the open source world.

    Will Microsoft stick it to him? He probably isn't the target. Will he be collateral damage? Probably. Microsoft wants someone like Google to adopt Mono so it can use the patent hammer to damage the competition. In that light, Mono is just bait.

  15. It's open core- not free software, not open source by ciaran_o_riordan · · Score: 4, Interesting

    From TFM:

    The new versions of .NET for the iPhone and Android will be source compatible with MonoTouch and Mono for Android. Like those versions, they will be commercial products, built on top of the open core Mono.

    "open core" is not free software, and it's not open source.

  16. Obsession by Muad'Dave · · Score: 1, Insightful

    Miguel's obsession with creating an open source version of .NET borders on mono-mania.

    --
    Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
  17. last sentence isn't a quote by ciaran_o_riordan · · Score: 1

    (bungled my html - that last sentence is a note from me, not a quote from the article.)

  18. Kool-Aid by think_nix · · Score: 0

    Miguel are you still drinking it ?

  19. 17 USC 1201(f) by tepples · · Score: 2

    and in many ways immune to patent litigation (although possibly not DMCA reverse engineering litigation -- I've heard that folks thought that was a possibility at one time)

    Reverse engineering for the express purpose of interoperability is not grounds for a DMCA suit according to 17 USC 1201(f). Say what you want about Universal v. Reimerdes, but I'd bet it would have gone down much differently if DVD Jon had waited until Linux had stable UDF support before releasing DeCSS.

  20. LOL ... by gstoddart · · Score: 1

    Wow, he's gonna port his open source implementation of .NET to iOS.

    That could rip a hole in the space-time continuum.

    --
    Lost at C:>. Found at C.
    1. Re:LOL ... by Anonymous Coward · · Score: 0

      Oh my god it's already happened!

      http://monotouch.net/

    2. Re:LOL ... by JSBiff · · Score: 1

      I may be wrong, but my understanding is that the version(s) of Mono that target iOS don't produce CIL (which is the .Net bytecode) binaries which then get executed on the Mono runtime like you would do for any other platform.

      I think, basically, it acts like a cross-compiler that creates an iOS native executable from .Net source code (on the compiling machine, it might still create the CIL binary, but then take the bytecode, and the bytecode for all libraries referenced, and compile that into an iOS native binary.

      If that's the case, that's not that radical an idea.

    3. Re:LOL ... by Anonymous Coward · · Score: 0

      That happened years ago. Where have you been?

  21. Oracle Java? Microsoft Mono? It's all the same... by Anonymous Coward · · Score: 0

    Great. If I want to work platform independ, I can decide if I want to code for Oracle's Java or with Microsoft's .NET. Both have nearly the same limitations with patents and corporate politics.

    On a second look my statement above sounds a little bit sarcastic. But it is not meant that way. I really like the Java/Scala/Groovy/Clojure ecosystem. And I am really curious to try .NET/Mono with C#/F#/IronPython/IronRuby. Both ecosystems are very advanced with regards to productivity tools and framework support. I would not want to miss any of them.

    It's a pitty that OpenSource needed Sun and Microsoft to kick-start both ecosystems. Now we have to deal with the consequences. But still better than not to have any of them.

  22. Isn't Xamarin... by digitaldc · · Score: 1

    ...a drug to help with the depressive side effects of internet addiction?

    --
    He who knows best knows how little he knows. - Thomas Jefferson
    1. Re:Isn't Xamarin... by instagib · · Score: 1

      I don't know, it really is a country club in Africa, but I think Miguel went for "Tamarin", which is a type of monkey. But unfortunately this name is already occupied by a Mozilla project, which strangely is some kind of scripting language, and to his dismay is also being used as the name for a Java framework. *head asplodes*

  23. Not a "Good Thing" by mrbluejello · · Score: 5, Insightful

    It is not a "good thing" to have Mono or .NET interoperability taken out of reach of Linux users. Interoperability layers such as Mono allow Linux systems to participate in networks that are dominated by Windows and other commercial systems. If it weren't for software like this, Linux systems may not be invited into some corporate networks, and would not get a seat at the table. The idea of a "pure" linux or no linux is going to continue having linux sitting out in the cold all by itself. Interoperability is crucial. If anything, we need more software like Mono, not less.

    1. Re:Not a "Good Thing" by oakgrove · · Score: 1

      It is not a "good thing" to have Windows API interoperability taken out of reach of OS/2 users. Interoperability layers such as Win16 allow OS/2 systems to participate in networks that are dominated by Windows. If it weren't for software like this, OS/2 systems may not be invited into some corporate networks, and would not get a seat at the table. The idea of a "pure" OS/2 or no OS/2 is going to continue having OS/2 sitting out in the cold all by itself. Interoperability is crucial. If anything, we need more software like integrated Windows API's, not less.

      There you go. I fixed it.

      --
      The soylentnews experiment has been a dismal failure.
    2. Re:Not a "Good Thing" by SCHecklerX · · Score: 1

      Mod this up.

      Windows APIs have no business in linux systems. And most intelligent companies, including the US military, and many fortune 500 companies, are already doing things on linux, using native linux tools. Even smaller shops, like the one I work for, get it.

      One of the things that killed OS/2 was its ability to run windows better than windows. So, why write native OS/2 code?

      Doing things the windows way on a linux platform instead of taking advantage of what makes linux linux is, to put it mildly, misguided.

    3. Re:Not a "Good Thing" by mrbluejello · · Score: 1

      By your reasoning, Linux systems have no business in Windows networks. That's not how the world works though.

      I don't know any business that has all of their internal software systems running in one API. In a world of infinite time and infinite resources, going for a "pure" linux environment is a noble one, but the real world has constraints, and learning curves, and existing skills, and business requirements that span multiple APIs and multiple systems.

      Let's say you have an entire backoffice system running on Linux. Your newest and largest customer that you just landed requires you to connect to their .NET invoicing system in order to submit and invoice and get paid. Would you stand your moral high ground saying "that's just dumb" and simply not do it? Would you fire your best client because they aren't on the FOSS bandwagon? Instead of running a simple .NET connector provided by your client, would you spend the time, money and resources re-implementing the connector and explain to your client why you need to "test" the connection?

      This whole FOSS purity is a tired argument left for the Stallmans of an outdated vision of the future. In a "perfect" world it is something to aspire to, but in the real world you must pick your battles one at a time, and not everybody uses FOSS. The world runs in a happy balance of proprietary and free software.

      Suggesting that Windows interoperability is what killed OS/2 is sorely incomplete. Everything around the OS/2 joint venture between IBM and Microsoft was complicated. If you recall, it was supposed to be a jointly owned platform, but then Microsoft went their own separate way and called their version Windows NT. It was the largely the same code base, which is why the interoperability existed. IBM and Microsoft are two very different companies, even more different at the time. Microsoft's business was the PC. IBM's bread-and-butter was the mainframe. How does OS/2 become successful in a company (at the time) dominated by 1970s era technology mainframe sales and maintenance contracts?

  24. Just Wondering by Anonymous Coward · · Score: 1

    Why I would choose to pay for .NET on Android over using the abundant and free tools for Java?

    I mean, I get putting Linux on every device known to humankind, just because it's cool to see things run Linux.
    I didn't realize the .NET community had their own version of this?

    1. Re:Just Wondering by mrbluejello · · Score: 1

      If you know .NET and want to deploy to a device, why have a steep learning curve when you can just use the tools you know? .NET runs on phones, servers, desktop PCs, microcontrollers (.NET Micro Edition), extending this to other operating environments is a logical choice. If Mono runs on a Mac, then the designer who insists on running a Mac doesn't need 2 computers at work (Mac for design, PC to run a required app). Interoperability is key, zealots that just stand in the way of this are impractical purists who don't care about users.

    2. Re:Just Wondering by shutdown+-p+now · · Score: 1

      If you just want to develop for Android, this doesn't make much sense.

      But suppose you want to write a cross-platform app that runs on both Android and iOS. That's where Miguel steps in and offers you to buy MonoTouch & MonoDroid from him - then you write the app in a single language (C#). You'd still need to have two separate view implementations, as both frameworks only directly expose the corresponding UI toolkits as .NET classes, but don't wrap them into any portable API.

      You could do the same in C++, but some people don't like things being too low-level, and you'll need to wrap UI toolkits (Obj-C on iOS, Java via JNI on Android) yourself.

  25. it's just a platform by spiffmastercow · · Score: 3, Insightful

    Seriously, isn't it a little juvenile to rally against a software platform just because it's based on something created by a company you don't like? And isn't it hypocritical to bolster Java when it's supported by Oracle, which has a reputation for destroying everything it touches?

    1. Re:it's just a platform by aaarrrgggh · · Score: 2

      For me, as a non-programmer, the rally against .net is a call for simple cross-platform functionality. We are spending a lot of money on ERP/accounting software for my company, and due to the .net backend and client, we are forced to add windows servers and to forego mobile access. It does have a web client... that just works in IE.

      The situation is typical in dealing with software that went down the .net path. It reduces flexibility and limits beneficial use.

    2. Re:it's just a platform by spiffmastercow · · Score: 0

      For me, as a non-programmer, the rally against .net is a call for simple cross-platform functionality. We are spending a lot of money on ERP/accounting software for my company, and due to the .net backend and client, we are forced to add windows servers and to forego mobile access. It does have a web client... that just works in IE.

      The situation is typical in dealing with software that went down the .net path. It reduces flexibility and limits beneficial use.

      Your situation is exactly one in which you would want mono though.. Your app could be converted to mono, and run on a Linux server. Mobile apps could be written in anything, as long as they communicate with your servers (probably through web services). As for your IE-only web site -- that's just bad programming on the part of your web developers.

    3. Re:it's just a platform by mridoni · · Score: 0

      No, it's typical for software written by people who don't understand the meaning of the word interoperability, or who were not given specifications in that direction. Yes, if you want to use Mono to run a large .Net project you have to plan in advance, but even if you decide to stay with the Windows backend, there's no reason not to have cross-platform clients, including mobile and web access; in your case it's just bad software design and even poorer planning that prevents them from existing. And, of course, you could also use Mono and have your backend on your OS of choice.

    4. Re:it's just a platform by cyber-vandal · · Score: 1

      The lack of trust in Microsoft's motives is completely and utterly justified. .NET is great, however the owner of the patents on it is not well known for being nice to its partners nevermind competitors.

    5. Re:it's just a platform by spiffmastercow · · Score: 1

      The lack of trust in Microsoft's motives is completely and utterly justified. .NET is great, however the owner of the patents on it is not well known for being nice to its partners nevermind competitors.

      Back in 2003 I would have agreed with you. Hell, even in 2007 I might have my doubts. But right now, MS is a fallen empire that sees itself in post-colonial terms. Microsoft doesn't care if you use mono; they're just thrilled you're programming in C#.

    6. Re:it's just a platform by newbish · · Score: 1

      For me as a programmer, the rally against Mono makes no sense. Also have you considered that maybe the other versions of ERP software that were available were either worse or much more expensive? There is nothing in .NET that limits use to IE if that's done then you have the vendor to blame not the technology. I work with an set of (very expensive) Oracle products every day that utilize JSP (Java Server Pages) and until a few months ago the only browser supported was IE 7.

    7. Re:it's just a platform by Anonymous Coward · · Score: 0

      You issue should be with the developer rather than Microsoft. .net is fully capable of supporting multiple browsers and it seems clear the software wasn't correctly evaluated prior to purchasing the software.

  26. Wine is just another subsystem by tepples · · Score: 1

    Having mono to run windows apps aka wine is great thing

    And most of the cheerleading for MonoTouch and Mono for Android that I've seen in Slashdot comments has been toward the aim of interoperating with .NET-only platforms.

    writing native Linux apps in mono [is] like using wine to write Linux apps

    And how is the latter bad? Glibc implements a POSIX-compatible subsystem, Glib and GTK+ implement a GTK+ subsystem, Qt implements a Qt subsystem, and Wine implements a Win32-compatible subsystem.

  27. Re:It's open core- not free software, not open sou by Anonymous Coward · · Score: 0

    Mono, the core project, is very definitely open source. However, just like with java, the mobile development platform is not open source.

    You've either being deliberately obtuse, or you've been living under a rock and haven't noticed that Oracle is suing Google over Dalvik. Care to clear up which it is?

  28. N-version programming by tepples · · Score: 2

    That company would be best advised to bite the bullet and implement it 3 times...using the correct and supported languages for the targeted platform

    Then what method do you recommend for ensuring that a program written in Objective-C, a program written in Java, and a program written in C# do exactly the same thing in all circumstances? Which N-version programming tools do you recommend?

    1. Re:N-version programming by Anonymous Coward · · Score: 0

      Hire competent programmers? Perhaps each versed in the native language of a target platform with some knowledge of the languages and tools used on the other platforms? Can't find these programmers? Look harder and spend the cash because they are out there.

    2. Re:N-version programming by Anonymous Coward · · Score: 0

      They shouldn't do the exact same thing if they are all running on different platforms.

    3. Re:N-version programming by Anonymous Coward · · Score: 0

      That company would be best advised to bite the bullet and implement it 3 times...using the correct and supported languages for the targeted platform

      Then what method do you recommend for ensuring that a program written in Objective-C, a program written in Java, and a program written in C# do exactly the same thing in all circumstances? Which N-version programming tools do you recommend?

      The best tool for N-version programming is a developer, although I've heard of some companies trying to do N-version programming with monkeys.

      Seriously, if a team can read specifications and produce a product in one language, why would one think that it's impossible to do the same in another language? We aren't talking about a difference of apples and airplanes here, it's more of a difference between Golden Delicious apples and Granny Smith apples.

    4. Re:N-version programming by tepples · · Score: 1

      The best tool for N-version programming is a developer

      Then what's the best tool for thoroughly testing N-version programming?

      Seriously, if a team can read specifications and produce a product in one language, why would one think that it's impossible to do the same in another language?

      For one thing, unless the specification for teams two and three is "your result must be bit-for-bit identical to the result of program produced by team one, reproduced below", things like the exact length and height of a character's jump or the exact behavior of the AI pathfinding are likely to differ from one implementation to another. For another, how shall I afford to pay all three independent teams every time the specifications change due to results of play testing?

  29. Ok, everybody. Two things: by Qbertino · · Score: 4, Insightful

    1st of all:
    Quit picking on Miguel. You may not share the same opinion as he on bigger issues, as do I, but treating him the way the majority here does is primitive. He deserves all respect and professional merit you can give. Unless you are Linus Torwalds, RMS or someone other of the rare few on which who's work his work is based on, you are not entitled to picking a fight with him or destructively ragging about his decisions and/or motives. The others actually aren't either, but at least they have a track record to back up their ego.
    He's done considerable contributions to the cause of FOSS, more than most of humanity anyway and way more than anybody of the wannabees here on slashdot could ever dream of accomplishing, so suck up any stupid and/or ignorant and/or snide remarks you may have ready and just STFU. Thanks.

    2nd: Mono may be a controversy in broader issues, but that's not to say it's not a good project. As for the product itself and products based of it: I know at least one that is a game changer and a major leap forward in its industry, that is based entirely on Mono and wouldn't be possible without it ( http://www.unity3d.com/ ). Cudos to Miguel and the Mono team for making it possible. I know for sure that the other large x-plattform around, Java, would have been beyond pointless as a foundation for realising this and would have failed miserably. Mono and Monodevelop are cool cross-plattform toolkits, and as far as I can tell they get the job done.
    Who can say that about their pet FOSS project?

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:Ok, everybody. Two things: by Anonymous Coward · · Score: 0

      ...they get the job done.
      Who can say that about their pet FOSS project?

      Not Miguel, that's for sure.

      *snickers*

    2. Re:Ok, everybody. Two things: by salparadyse · · Score: 2

      you are not entitled to picking a fight with him

      You mean pick.
      And yes we are.

      There is no law that says that critics may only come from a select class.
      Criticising things on an ideological basis is open to all.

    3. Re:Ok, everybody. Two things: by tokul · · Score: 1

      Quit picking on Miguel.

      This is slashdot. What else do you expect?

      He's done considerable contributions to the cause of FOSS

      Scratch "to the cause of" part. Getting in bed with MS does not contribute anything to the cause of FOSS.

    4. Re:Ok, everybody. Two things: by Anonymous Coward · · Score: 0

      1st of all:
        He deserves all respect and professional merit you can give.

      ROFL.

    5. Re:Ok, everybody. Two things: by Anonymous Coward · · Score: 0

      I know at least one that is a game changer and a major leap forward in its industry, that is based entirely on Mono and wouldn't be possible without it ( http://www.unity3d.com/ [unity3d.com] )

      Oh please, Unity news are the most irritating posts on monologue, precisely because it's not a game changer. Company uses open source software. Company still doesn't care to release their stuff on Linux. Seen it before.
      Miguel himself treats Linux as the least important platform, releasing Monodroid for Windows and OSX first. And they're busier writing Visual Studio plugins than improving Monodevelop.
      The Mono ecosystem is neither very open, nor even targeted at the open source community.

    6. Re:Ok, everybody. Two things: by Anonymous Coward · · Score: 0

      I will make it just as simple for you......

      Just STFU. Thanks.

      Linus and RMS.. both vote, NO. 2 Strikes.....

      Attachmate has kicked them out..... STRRIKKKKKEEE THRREEEEEEEEE! YOUR OUT!

      I applaud attachmate for kicking him and the rest of the trash to the curb. There is NOTHING GOOD to come of this project...

      This is the atypical e3 method of a certain Washington based company. In addition there are HUGE ISSUES with portions of the language which are PATENT AND IP LANDMINES!

      Yes... yes... we know the standard BS line... But its ISO approved, and the ever so benevolent emperor has released the rest under a very lax license... The parts under the ISO spec may be good to go, I disagree, but the parts that are not in the ISO spec and only released under some license by a company who is a known liar and anti Linux... NO THANKS!

      As for projects that are useful that came from this disease... really? ? YOU want to hold up unity as your poster child?!?!?!? SERIOUSLY? ? ? ? That has been a resounding and complete FAILURE for the ONLY DISTRO pushing it.... I've rejected it not only for its programming source, but it programmer, and its ties to another DE which I don't approve of either.

      monoboi and monkeyboi make for a good couple, except one is not accepting the advances the other is making... how many times do you have to get rejected to get the monoboi? ? ? This is twice this year already...

      I don't have a pet OSS project, (free... I don't think that means what you think it does! has nothing to do with it)... but my pet OS, Linux, has done more good collectively than any of monobois projects and that includes that worthless DE of his as well. Its garbage... It stinks just like the stinky troll foot of its logo and this projects logos... Ever been to the zoo and watched the monkey(s) and what they do? ? ?

      So take your own advice and just STFU. Thanks. Enjoy the Flavorade!

    7. Re:Ok, everybody. Two things: by jedidiah · · Score: 2

      Miguel is not the pope. Stop trying to treat him as such.

      This is Slashdot, check your Lemming mindset at the door.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    8. Re:Ok, everybody. Two things: by Anonymous Coward · · Score: 0

      You must be new here.

      Until Miguel started his Mono project, he was one of the patron saints of the Slashdot crowd. It was mono--and ONLY mono--that changed everyone's tune here about him. Slashdot has long been a bastion of pro-GNOME and pro-Miguel, up until Mono. With that, I'd say he deserves the criticism.

      I highly doubt the assertion that Miguel has made "considerable contributions." He has perpetual ADD and can't seem to focus on any one project and see it through. He started GNOME...and then ran off to create Ximian and Evolution. Then he ditched that to work on Mono. GNOME's eventual maturing had little to do with Miguel. It was under his watch that the libraries magically went from version 0.3 to 0.99 hey-presto overnight, leading to the rotten bug-fest that was Gnome 1.0.

    9. Re:Ok, everybody. Two things: by Anonymous Coward · · Score: 0

      Yes. Quit picking on Miguel. After all the guy's a genius. Well at least when he's copying Microsoft.

    10. Re:Ok, everybody. Two things: by gmhowell · · Score: 1

      Looks like Chris Crocker is white knighting for someone else now...

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
  30. Mono is/was widespread? by vlm · · Score: 1

    beginning of the demise of widespread use of Mono and other .NETiness in open source software

    This seems to VERY incorrectly imply there once was, or currently is, widespread use of Mono and other .NETiness in open source software. Is it a yogi-ism to say its so widespread that nobody uses it anymore?

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  31. shouldn't it be called Duo by Locutus · · Score: 3, Insightful

    Since Attachmate didn't sell Mono to this Xamerin group are there not two versions of Mono? That would then be a Duo. Because two Mono's don't make it right.

    That reminds me, Miguel already has a dual personality with his proclaimed love of open source yet his constant admiration for everything made by Microsoft.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    1. Re:shouldn't it be called Duo by Anonymous Coward · · Score: 0

      Since Attachmate didn't sell Mono to this Xamerin group are there not two versions of Mono? That would then be a Duo. Because two Mono's don't make it right.

      That reminds me, Miguel already has a dual personality with his proclaimed love of open source yet his constant admiration for everything made by Microsoft.

      LoB

      Actually mono has always been open source, so attachmate doesn't own it to begin with.
      Second, Miguel owns all Apple devices and no longer user Windows (if in fact he ever did)

    2. Re:shouldn't it be called Duo by dhavleak · · Score: 0

      That reminds me, Miguel already has a dual personality with his proclaimed love of open source yet his constant admiration for everything made by Microsoft.

      Weak. The guy that gave the world Gnome has already benifited you more in your life than you can ever hope to repay him.

    3. Re:shouldn't it be called Duo by Anonymous Coward · · Score: 0

      No, two Monos do not make a Duo. It makes a pair of monkeys.

    4. Re:shouldn't it be called Duo by Anonymous Coward · · Score: 0

      De Icaza has already indicated his priorities when it comes to open source. In http://tirania.org/blog/archive/2011/Feb-14.html he celebrates Nokia switcing from an open source mobile OS to a closed source, Microsoft platform. And in addition, in the comments, he says that had they switched to android--which even supports his beloved Mono--he would have just reacted with a "blah, another android phone"

    5. Re:shouldn't it be called Duo by Anonymous Coward · · Score: 0

      Dude, you gotta admit, the Death Star was pretty fuckin' sweet, even if it was designed and developed by the Empire, for nefarious purposes.

      Not all great innovation comes from the FOSS community, and, in fact, MS actually has really good stuff in their Research division. It just mostly gets buried under crap from the product side. As a community, we're smart to pay attention, and learn from, some of the best researchers in the world (especially because we may be their brilliant ideas' only chance for seeing the light of day).

    6. Re:shouldn't it be called Duo by Locutus · · Score: 1

      the Death Star was cool but the copy was just a bunch of big Spaceballs. Besides, it was the super weapon which was cool, the support systems around it ended up causing its parts to be very quickly separated along with everything else around it.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  32. It serves a need, so it is useful... by GrumpyGeek · · Score: 1

    I am pretty sure the Unity Game development platform (http://unity3d.com/) is .Net based and uses Mono to run on iOS and Android. This is a nice game development tool made cross platform by Mono, so I would say Mono qualifies as useful. I am sure there are other examples.

    1. Re:It serves a need, so it is useful... by Anonymous Coward · · Score: 0

      Unity itself isn't .NET based. The scripting components themselves are, however.

      I'm not a big .NET fan (Java/OSS guy) but I think Unity's use is pretty cool.

  33. PhoneGap can be slow to respond by tepples · · Score: 1

    My meager Google research indicates that PhoneGap can be slow to respond, especially for applications that need to perform a lot of calculation. Apple finally introduced JIT execution of JavaScript in iOS 4.3, but only within the Safari app; UIWebView applications such as those made with PhoneGap still use the interpretive engine. (Yes, I know about the security issues of running JIT in the same process as untrusted code, but Apple chose to get iOS 4.3 out the door before refactoring UIWebView to sandbox a view in its own process.)

  34. How to afford, and how to verify? by tepples · · Score: 1

    So how does a startup afford to "spend the cash"? And once the allegedly "competent programmers" have checked in code, how does the lead engineer verify automatically that the code does in fact behave identically?

  35. Miguel, let it die by bl8n8r · · Score: 0

    .NET was a mostly foiled attempt of microsoft to do the same thing with C that they did to Netscape. Why hand that over to Microsoft by implementing some cross-platform version of a noose they can hang you with? They are bad enough when the law *isn't* on their side.

    I don't understand what would drive anyone to do this unless they are on the Microsoft bank-roll.

    --
    boycott slashdot February 10th - 17th check out: altSlashdot.org
  36. Re:It's open core- not free software, not open sou by Anonymous Coward · · Score: 0

    So, it's proprietary software. There is no need to come up with clever-sounding euphemisms such as this "open-core" nonsense. It's proprietary software which happens to market itself on top of a open-source project.

  37. Mono? by Anonymous Coward · · Score: 0

    Homer: Mono... D'oh!

  38. Compare Microsoft to Nintendo and Sony by tepples · · Score: 1

    Why hand that over to Microsoft by implementing some cross-platform version of a noose they can hang you with?

    Compare the policies of the three video game console manufacturers:

    • Microsoft: Individual developers may work from home as long as their products use 100% pure .NET. No pointers, no P/Invoke, no Reflection.Emit, final destination.
    • Nintendo: No developers working from home allowed at all. I can provide citations if you wish.
    • Sony: SCEA's developer relations site has been down for over a month, but I've read rumors that its policy is like Nintendo's.

    In this case, Microsoft is the least of three evils.

    The cross-platform aspect just lets a developer share the game logic between the Xbox 360/Windows version of a game and the version for other platforms. Otherwise, a port to or from the platform is a complete line-by-line rewrite that introduces errors and requires subsequent changes to be made twice.

    1. Re:Compare Microsoft to Nintendo and Sony by Bill_the_Engineer · · Score: 1

      How does Microsoft letting you use .NET on a XBox, both of which are made by Microsoft, apply to bl8m8r's assertion that it may be a bad idea to spread the use of .NET on other platforms? I can only infer that the dangers he warns us about are:

      1. Using a non-Microsoft product to develop .NET applications may open yourself to litigation from Microsoft or Oracle. Microsoft has a cross licensing agreement with Oracle that resulted from a court settlement with Sun. Novell had a patent deal with Microsoft, I assume Xamian does not.

      2. You risk vendor lock in with .NET because of #1.

      Anyway I don't understand your point because your example doesn't address the above dangers. Personally I think Java vs. .NET is a better example than bl8m8r's Microsoft vs. Netscape.

      The cross-platform aspect just lets a developer share the game logic between the Xbox 360/Windows version of a game and the version for other platforms. Otherwise, a port to or from the platform is a complete line-by-line rewrite that introduces errors and requires subsequent changes to be made twice.

      Officially .NET is only cross platform with Microsoft products (eg. Windows and XBox). If my goal was to really be cross platform with other OS, using a language rather than a toolkit such as QT, I would pick Java or .NET since it is officially supported on Windows, Linux, and OSX by Oracle, and other OS through OpenJDK.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    2. Re:Compare Microsoft to Nintendo and Sony by Bill_the_Engineer · · Score: 1

      "Java or .NET" should have said "Java over .NET". The "ve" was omitted and I didn't catch it until after submit.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  39. Xbox 360 is not an also-ran by tepples · · Score: 1

    Given that, why would you want to fall for using the platform they control( MS .Net) to create applications for the 2 dominant phone platforms, iOS and Android, so you can get the also-ran Windows Phone 7

    True, Windows Phone 7 might be considered an "also-ran" worthy of ignoring, but Xbox 360 is not. Like applications for Windows Phone 7, Xbox Live Indie Games also use the .NET Framework.

  40. The only set-top game platform for micro-ISVs by tepples · · Score: 1

    You bitch to Microsoft for not making that possible by not allowing native code.

    I see no reason for Microsoft not to just ignore such complaints. Microsoft knows that it provides the only console for games developed by micro-ISVs. So it offers a Hobson's choice: develop in XNA, or just choose not to publish your game on any console at all.

  41. Re:It's open core- not free software, not open sou by wasabii · · Score: 1

    I think the sentence specifically does not say what you think it says.

  42. Good Xamarins want to lend a helping hand by Anonymous Coward · · Score: 0

    ...but they sometimes end up as roadkill.

  43. Good Luck Miguel by kervin · · Score: 1

    Haters are gonna Hate. That's just what they do.

    I wish Miguel and his team the best of luck. I was actually reading Slashdot when Miguel started Gnome, actually remember the email announcement. Gnome was an incredible success. His other ventures all got bought out ( a successful exit strategy ).

    If Xamarin would except micro-investments ( ie. 100K ), I'll be first in line to sign up. I've got something in the 401K, the wife has this ( morbidly weird ) funeral savings I might be able to get at. Heck, the kids got a piggy bank they watch like hawks; luckily they fall asleep early.

    1. Re:Good Luck Miguel by walterbyrd · · Score: 0

      Haters are gonna Hate. That's just what they do.

      By "haters" do you mean people who hate being scammed by Microsoft?

    2. Re:Good Luck Miguel by gbjbaanb · · Score: 1

      the best solutions to all this is for all of us to really get behind Miguel and Xamarin, boost its popularity (well, at least on message boards, blogs, and forums), then Microsoft comes along and gives Miguel $1bn for the company, he f***s off to a desert island to tell dusky maidens about his great .NET is, Microsoft is $1bn closer to getting rid of Ballmer and subsequently being broken up by the accountants, and we all laugh as we stop pretending to use it on Linux and continue writing our apps in C and Python.

      See, everyone's a winner.

      PS. your 100k would be better spent on other activites - invest in Arduino, or Android hardware projects. Invest in providing software to the kind of people who cannot afford it, who still cannot afford a MonoDroid licence. Don't get too focussed on a bit of software that is targetted at an incredibly niche market. Spread your view to the possibilities that all the other stuff is making available to us.

  44. Look up "Bitkeeper" by Anonymous Coward · · Score: 0

    It IS enough to get the license changed and rescinded.

  45. System.Reflection.Emit not in XNA by tepples · · Score: 4, Informative

    And like you noted, .NET apps or games can be written in many different languages. He seems to like Python

    I was under the impression that IronPython and other DLR languages required System.Reflection.Emit, which was not present in the subset of the .NET Framework supported by Xbox 360 and Windows Phone 7 last time I checked.

    All the languages can also use the huge library of code and API's.

    The libraries also have to be written in pure .NET code, unlike in Python where it's common to package a C++ library as a module.

    1. Re:System.Reflection.Emit not in XNA by KingMotley · · Score: 1

      The libraries don't have to be in .NET code.

    2. Re:System.Reflection.Emit not in XNA by tepples · · Score: 1

      The libraries don't have to be in .NET code.

      They do if you want to deploy to Xbox 360 or Windows Phone 7. Otherwise, the device will reject the assembly because it contains something other than verifiably type-safe IL. Or since when has Microsoft changed this?

  46. MOD PARENT UP by knapper_tech · · Score: 1

    Java is one language. Python is one language. With .Net-like technology, FOSS can invade the windows space like never before. There's the potential to share business logic on everything from Android to XNA. Wake the F*@& up. The growth of cross-platform FOSS breaks down the walls that separate platforms and prevent cross-platform competition from occurring.

    The day that FOSS comes up with a totally free CLR and CIL that allows static inclusion of the VM in the binary is they day that people can talk trash about Mono as if FOSS already has a better solution.

    --
    "There are some people that if they don't know, you can't tell them." ~ Louis Armstrong
    1. Re:MOD PARENT UP by Anonymous Coward · · Score: 0

      Java is a specification.
      Java is a language.
      Java is a virtual machine.
      Java is a standard library.
      Java is a platform.

      Many languages run on the Java platform.

    2. Re:MOD PARENT UP by Anonymous Coward · · Score: 0

      And Google is being sued by Oracle (Sun) over Java patents. So, Java is bad. It is not a standard if Oracle only allows you to run their version of the JVM. But, I guess its okay to you that Google is being sued by Oracle simply because Google is not the evil Microsoft.

      Many languages run on Mono / .NET too. Plus, the CLI and C# are ISO / ECMA standards. Java is not an ISO nor ECMA standard because Oracle (Sun) wants to have control over it. JCP is a joke because it gives control to Oracle (Sun).

  47. No Android-powered game console by tepples · · Score: 2

    Otherwise, there is no way I'm going to use a second class dev environment on my first choice platform. Here is a list of the top grossing games on Android

    Does an Android-powered device capable of running apps come in a set-top form factor? I haven't seen one. If not, then Xbox 360 is pretty much the only platform for indie console games, and any such game needs to be written in .NET so that it can run in the XNA environment.

    1. Re:No Android-powered game console by oakgrove · · Score: 1

      I've looked high and low. None of the top selling apps on Android are written in mono. All of the developer documentation for android is written assuming you will be using Java. If I run into any weird issues or bugs in Android, I'm going to be in a much better position to get help if I'm using the officially sanctioned development methods. The Android SDK is just going to enable me to write a better app. I'd rather write the best application my abilities will allow rather than hamstring myself worrying about getting it running on the Xbox. Not to mention the fact that on Xbox, I will never be on the same playing field as the real game developers. With Android, I am. And Windows Phone 7 doesn't have enough market share to matter and until it does, it isn't a factor.

      --
      The soylentnews experiment has been a dismal failure.
  48. Commercial Support by kvvbassboy · · Score: 2

    Can someone tell me who uses Mono "commercially"?

  49. Do you know what open core is? by ciaran_o_riordan · · Score: 1

    Take some free software, add non-free software, keep the source code for the latter to yourself, and do some advertising emphasising the free software base.

    The quote I gave from TFM seems to say pretty clearly that this is their model. What's your point?

  50. i hope for your sake by circletimessquare · · Score: 1

    you grow to understand informality, and recognize the effort to be formal and proper all the time is pointless and without merit

    that some brittle mind expects formality where none is due, like in a fucking comment board, is someone that does not deserve any respect. demonstrate to me flexibility of mind, and i will begin to consider your opinions worthy of consideration. otherwise, fuck off

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:i hope for your sake by Anonymous Coward · · Score: 0

      As a reader, otherwise uninvolved in your discussion, I feel I should let you know that you lost that exchange, quite badly.

    2. Re:i hope for your sake by Anonymous Coward · · Score: 0

      Actually, from the same position as you, I feel that circletimessquare was pretty much on-the-dot correct.

  51. What instead of Xbox Live Indie Games? by tepples · · Score: 1

    .NET has no business being on iOS

    Then how do you recommend making one application whose business logic runs on Windows Phone 7 and iOS, or one video game whose game logic runs on both Xbox 360 and iOS?

    Simple, don't bother with a Windows Phone 7 port.

    I mentioned Xbox 360 too. What alternative to XNA Game Studio, App Hub, and Xbox Live Indie Games do you recommend?

    1. Re:What instead of Xbox Live Indie Games? by aristotle-dude · · Score: 1

      .NET has no business being on iOS

      Then how do you recommend making one application whose business logic runs on Windows Phone 7 and iOS, or one video game whose game logic runs on both Xbox 360 and iOS?

      Simple, don't bother with a Windows Phone 7 port.

      I mentioned Xbox 360 too. What alternative to XNA Game Studio, App Hub, and Xbox Live Indie Games do you recommend?

      Do a cost benefit analysis of whether it is worth developing for both platforms or choose the platform that will bring you the most income if you cannot afford to have two development streams. Xbox live is big but it is also really crowded so you might get lost in the noise.

      The .NET framework is my bread and butter in the business world but if I was developing mobile apps and/or games, I would probably concentrate my development on iOS if the app/game was not online centric. If you have an app that relies on network services then you can write those on .NET if you want and just write the client UI using the best framework for each platform that you choose to target. My motto is to use the best tool for the job. You cannot get stuck on thinking that everything has to be on one codebase especially if it is highly network dependent.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
  52. J# on XNA by tepples · · Score: 1

    Officially .NET is only cross platform with Microsoft products (eg. Windows and XBox). If my goal was to really be cross platform with other OS, using a language rather than a toolkit such as QT

    Qt is not ported to Xbox 360.

    I would pick Java [over] .NET since it is officially supported on Windows, Linux, and OSX by Oracle, and other OS through OpenJDK.

    Say I write my video game in Java. How well does J#, Microsoft's implementation of the Java programming language for the .NET Framework, work with XNA?

    1. Re:J# on XNA by Bill_the_Engineer · · Score: 1

      My point was that you are comparing "apples to oranges". The parent was talking about using Mono on other operating systems, and you are talking about using .NET on XBox and Windows.

      .NET is the best tool for the job when you are talking about making games that run on both XBox and Windows especially since they both use the SDK built and supported by Microsoft. I wonder how the performance of .NET compares to non-XNA games running on the XBox.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    2. Re:J# on XNA by tepples · · Score: 1

      The parent was talking about using Mono on other operating systems, and you are talking about using .NET on XBox and Windows.

      .NET is the best tool for the job when you are talking about making games that run on both XBox and Windows

      Then what's the best tool for making a game that runs on both Xbox 360 and a non-Microsoft platform?

      I wonder how the performance of .NET compares to non-XNA games running on the XBox.

      I'd imagine that only licensed professional Xbox 360 developers with a dedicated secure office and a previous title on another platform are privy to this information.

  53. Better than not having a playing field at all by tepples · · Score: 1

    I'd rather write the best application my abilities will allow

    And have no audience. If my game design includes a mode where multiple players share a screen, as opposed to always needing a separate device and copy of the game per player, the only platforms I've found so far that allow that are XNA and home theater PCs. There appear not to be enough home theater PC owners among my audience to make development of a home theater PC-optimized game worthwhile, though I'd love to see evidence to the contrary. This leaves XNA.

    Not to mention the fact that on Xbox, I will never be on the same playing field as the real game developers.

    I contend that not being on the same playing field as developers in the major cities is better than not having a playing field at all.

    1. Re:Better than not having a playing field at all by oakgrove · · Score: 1

      And have no audience.

      What are you talking about? Android has the highest market share of any smartphone and shows no sign of slowing down.

      If my game design includes a mode where multiple players share a screen, as opposed to always needing a separate device and copy of the game per player

      So, you are saying I need to use mono to write Android games so that that same game can be run as split screen multi-player on xbox? What about when it is on the phone? First that doesn't even make sense and second, talk about the tail wagging the dog. And if I make a game that works on both platforms, which one do I gimp? The Xbox is obviously more powerful so do I dumb it down to a smartphone level? The phone has a touchscreen and myriad sensors like gps, accelerometer, ambient light, etc. How do I transate that? You have outlined a recipe for a crappy game. Plain and simple and I will have no part of it. At this point, I have to assume that you have run out of anything insightful to say and are arguing just for the sake of it.

      I contend that not being on the same playing field as developers in the major cities is better than not having a playing field at all.

      As I've illustrated, the Android "playing field" is plenty big.

      --
      The soylentnews experiment has been a dismal failure.
  54. Bad slashdot poster (me) by npsimons · · Score: 1

    And right there in the summary, it says De Icaza's company will make .NET dev tools for iOS and Android. Bad me, for not RTFS. What can I say? I come to slashdot for the comments. I still think that De Icaza is tilting at windmills (but with less wits and foresight than Quixote) and .NET on Android will be the second (at best) preferred dev tool. Not to mention that the legal issues (and MS changing C# at a whim and breaking tons of existing apps) still makes this a non-starter. Yes, good riddance .NET and C#. Some of us haven't had to think about MS for years, and would rather not ever have to again.

    1. Re:Bad slashdot poster (me) by Richard_at_work · · Score: 1

      Everything you said is still personal opinion - no one is saying Microsoft was "first" with any of C#'s features, but its damn nice having those features all in one language. Thats what Microsoft brings to the party - feature wise, C# and .Net is ahead of Java, a language I personally dislike but don't expect you to dislike.

      C# and .Net also tend to be very stable targets - new features get rolled into new platform versions, old platform versions remain as they were. You can still develop .Net 1 based applications with no issues, so wheres the problem with MS "changing C# at a whim"? Changes they make don't break anything.

      You are welcome to your opinions, but your presentation seems to require me to agree with your opinions.

  55. Has it occurred to anyone by Progman3K · · Score: 1

    That to avoid litigation around mono, one should NOT develop anything in .NET

    --
    I don't know the meaning of the word 'don't' - J
  56. Do you want completely unrelated games? by tepples · · Score: 1

    Android has the highest market share of any smartphone

    I'm talking about platforms other than smartphones. Not everybody has a smartphone because plans cost money, and some people prefer to play in person with friends and family.

    The Xbox is obviously more powerful so do I dumb it down to a smartphone level?

    You'd write the gross physics and enemies' action instructions to work identically on both platforms: a character can run this fast and jump this high, enemies deal this much damage, etc. (How much "dumbing down" does this require?) Then you'd probably write a separate graphics engine per platform.

    The phone has a touchscreen and myriad sensors like gps, accelerometer, ambient light, etc. How do I transate that?

    As with the graphics, you'd write a separate input tier per platform. The input engine would interpret what the player has done and send movement commands to the game logic. An input engine for Android or WP7 would translate tilting the device, pressing on-screen buttons, tapping specific objects or areas of the screen, etc. into "turn this way" and "move that way" and "swing your stick". On Xbox 360, it'd translate movements of the Control Stick and button presses into actions. But the core game logic would implement the rules of the game that don't vary per platform. Please see Wikipedia's articles about the model-view-controller paradigm and multitier architecture.

    You have outlined a recipe for a crappy game.

    Please correct me if I'm wrong, but I take it you want one game exclusive to Android and a completely unrelated game exclusive to Xbox 360.

    1. Re:Do you want completely unrelated games? by oakgrove · · Score: 1

      I'm talking about platforms other than smartphones. Not everybody has a smartphone because plans cost money

      Well, obviously, Android comes on more than just smartphones. I just figured that went without saying.

      You'd write the gross physics and enemies' action instructions to work identically on both platforms: a character can run this fast and jump this high, enemies deal this much damage, etc. (How much "dumbing down" does this require?) Then you'd probably write a separate graphics engine per platform.

      As with the graphics, you'd write a separate input tier per platform. The input engine would interpret what the player has done and send movement commands to the game logic. An input engine for Android or WP7 would translate tilting the device, pressing on-screen buttons, tapping specific objects or areas of the screen, etc. into "turn this way" and "move that way" and "swing your stick". On Xbox 360, it'd translate movements of the Control Stick and button presses into actions. But the core game logic would implement the rules of the game that don't vary per platform. Please see Wikipedia's articles about the model-view-controller paradigm and multitier architecture.

      Thank you for the links and thank you for going through the trouble to explain your point thoroughly. We obviously have a difference of opinion. I do not believe it is possible to create a really compelling game that works on xbox and android with mono that will compete with the best each platform has to offer respectively. There will be little corners here and there you will have to cut and when you're done, you may as well have just developed natively and been done with it. A good example is quake 3 (and this is pure example, my point does not hinge on it). A fantastic game in its day. It has been ported to Android (as well as everything else). Everything from the physics engine up was designed with a mouse and keyboard in mind and it shows. It's terrible on Android. Yeah, it looks great but that is the end of it. The onscreen controls are imprecise. It just doesn't feel right. Working on two completely disparate platforms like a console gaming device and a touchscreen cell phone is going to require ground up compromises and it's never going to feel quite "right" on either one. Or if it feels good on one, it won't on the other. This has happened to many games ported between PC and Playstation/XBox. Oblivion was terrible for this very reason.

      So, yes, I...

      want one game exclusive to Android and a completely unrelated game exclusive to Xbox 360.

      --
      The soylentnews experiment has been a dismal failure.
    2. Re:Do you want completely unrelated games? by tepples · · Score: 1

      I'm talking about platforms other than smartphones. Not everybody has a smartphone because plans cost money

      Well, obviously, Android comes on more than just smartphones. I just figured that went without saying.

      But in most cases, you don't get OHA Android with Google's Android Market unless you get either a phone or a 3G tablet. Most PDAs and Wi-Fi-only tablets, such as Archos and Coby products, come with AOSP Android, which relies on AppsLib and Amazon Appstore. I was thinking more along the line of there not being a Android-powered game console.

      Working on two completely disparate platforms like a console gaming device and a touchscreen cell phone is going to require ground up compromises and it's never going to feel quite "right" on either one.

      Ideally, something like Xperia Play, an Android-powered phone by Sony Ericsson with a slide-out gamepad instead of a keyboard, would help bridge this gap. But in practice, I know what you're talking about: I tried Tetris on my aunt's iPhone, and EA handled it like crap compared to Tetris DS. Whether this is an inherent limitation or just EA not caring is hard to tell because The Tetris Company won't let anyone but EA make tetromino games for phones.

  57. Rewriting code legalities by kripkenstein · · Score: 5, Informative

    If it's under the GPL and LGPL, it's going to be a rough case Attachmate would be making, considering that it's open licensed and they just kicked the team to the curb.

    The FOSS code is not a concern here.

    The issue is the proprietary code that Miguel et al worked on in Novell, the Android and iPhone runtimes. That is owned by Attachmate now, and this new startup contains exactly the same coders, who are intentionally going to write the exact same product from scratch - they will be 100% "source compatible" with the old runtimes.

    So legalities are a reasonable concern. Even if no code is copied, the same people writing the same product - immediately after writing it the first time - may lead to basically the same code being written. It might be hard to prove no code was copied even if none was. Lawsuits are filed for much less.

    Of course, this only matters if Xamarin is a big success - no one sues a failure. Time will tell.

  58. kinda makes you wonder doesn't it? by Anonymous Coward · · Score: 0

    Kind of makes you wonder if Miguel's also on M$'s payroll in one way or another.

  59. What's the point of .MONO by doperative · · Score: 1

    I can't for the life of me understand De Icazas motovation in expending so much energy in cloning a Linux version of dotNET, functionality that in some-ways-or-another, already exists on Linux?

  60. Nintendo's requirements are even stricter by tepples · · Score: 1

    How important are XBox Live Indie Games really? XBox is basically the second most popular gaming console, and is behind by a large margin.

    Xbox Live Indie Games is the only console platform available to micro-ISVs. Wii is the market leader, but Nintendo platforms are not for a company's first title, nor are they for home-based businesses. Nintendo requires "relevant game industry experience" and "that companies are working from a secure business location [...] not located within a personal residence."

    1. Re:Nintendo's requirements are even stricter by Jason+Earl · · Score: 1

      Thanks for the post, that was informative. In fact, it was informative enough that I actually did a little research. Yes, it appears that the XBox Live Indie Games is unique in the console industry. It also appears to be somewhat of a ghetto. Microsoft sets the price points, limits the playtest time, etc.

      If you *really* want to put your game on a console Microsoft is the only game in town. The fact that your game would probably be easy to port to the PC almost certainly helps.

      I suppose it is even theoretically possible that you might want to take your XBox Live Indie Game and try and port it to Android or iOS. If that were the case then the MonoDroid and MonoTouch tools might be useful. Of course, these are now Attachmate property and have nothing to do with Xamarin, but that's another story.

  61. Application logic vs. presentation by tepples · · Score: 1
    Anonymous Coward wrote:

    They shouldn't do the exact same thing if they are all running on different platforms.

    An application can be separated into two components: application logic, which does not vary per platform, and presentation, which does vary. Versions of a game for different platforms would have separate graphics and input engines for each platform, but ideally, they would share the application logic, which determines for example how high a character can jump, how close two objects can approach, how much damage a character takes, and how non-player characters will act. See also Model-view-controller and Multitier architecture.

  62. Ballmer is still calling the shots by Anonymous Coward · · Score: 0

    Are you stupid? considering your inability to use caps, probably. Ballmer is still calling shots in the company, and now he's calling all of them; so nothing has actually changed.

  63. ObWayne by Anonymous Coward · · Score: 0

    "I thought I had Mono for a whole year once. Turned out I was just really depressed."

  64. Ideology for dummies by Anonymous Coward · · Score: 0

    You don't understand what the argument is about you fool.

    It isn't about this technology being better or that technology being worse.

    It is entirely about the price you have to pay, and the availability of the technology.

    Almost all of the arguments which spiral around the issue of free and non-free software are concerned with the various ways in which companies manipulate their customers in order to tie them into their product. The license is by far the most obvious mechanism used for that purpose. Patents are a close second.

    Nobody is saying C# is crap. Nobody cares. What some people are saying is that C# on Linux is part of a plan to undermine the open source, free software platform by introducing software into the heart of the system which can lay it open to patent claims. Others believe it is simply a means of luring open source software developers and users away from Linux (Microsoft's worst nightmare is that there could be a shift from their proprietary platform to a GPL'd one). They're probably right.

    If I hear one more dimwit say, "I don't care about all these arguments I just use the technology that does the job" I swear I will smack them on the nose with a baseball bat (not literally though).

  65. That's Nice Grandpa by Anonymous Coward · · Score: 0

    We've all got 'em, bigoted grandparents that can't quite let the old race conflict go. The younger generations just roll their eyes during the periodic tirades and say "that's nice grandpa." That what we have here. The older portion of the Linux community is constantly trying to resurrect the Microsoft threat of the 80's and 90's to rally the troops. Kids coming out of college just don't see it like that. To us it's all good. Microsoft has some cool stuff, Oracle's got some stuff. There's lots of great open source stuff. Can't we all collaborate, hack, mash and... get along? Slashdot still uses an icon of Bill Gates as the Borg for its Microsoft-related posts, for crying in the night. Could you get any more out-of-touch? .Net on Linux is just another great tool in a developer's toolbox.

  66. it's just a law suit by Anonymous Coward · · Score: 0

    Seriously, isn't it a little juvenile to rally against a software platform just because it's based on something created by a company you don't like? And isn't it hypocritical to bolster Java when it's supported by Oracle, which has a reputation for destroying everything it touches?

    You do have a point about Oracle, but It isn't a matter of a company I "Don't like" it is a matter of a company I "Don't Trust". I've been around long enough and watched MS and their dirty tricks I know what they are capable of and Mono is just a back door for them to sneak in through. Of course I don't have any trust in Oracle which is the reason some 600 Solaris servers are being replaced in our data center with Debian Linux.

    I do know I will not base how I make a living on any technology that can be bought and sold like a two dollar whore again.

    As far as I'm concerned he is just wasting his time. Hell I quit using Gnome because it now loads Mono. You know I wouldn't want to infringe on any MS patents and the best way to do that is NOT use MS code. Besides there are a ton of languages that do a far better job than .NET and they are completely open and do not infringe on any MS patents

    See patents do work. They keep shit out of my DC.

  67. Readability and informality are different by Anonymous Coward · · Score: 0

    Readability and informality are two different things, but you are too stupid to understand the difference.

    For instance this message is informal, but readable. Your message is simply unreadable because it does not use caps, and has sentences broken between the subject and the body.

    Now for your sake you stupid ass, I hope you have learned something.