Slashdot Mirror


Mono Comes To Android

hairyfeet writes "After releasing Monotouch for iPhone which allows c# development on iOS, Novell has announced the availability of Mono for Android. Will this give us the 'one language to rule them all' that Java failed to bring, or will the bad blood between the F/OSS groups and Microsoft make this a dead end?"

257 comments

  1. Mono? On my Android? by Anonymous Coward · · Score: 4, Funny

    Guess I won't be kissing it for a week or so.

    1. Re:Mono? On my Android? by broknstrngz · · Score: 1

      That's what happens when you pair it to slutty devices, like the iPhone, over Bluetooth.

    2. Re:Mono? On my Android? by by+(1706743) · · Score: 2

      You could just hold the phone upside-down. More fun for everyone!

    3. Re:Mono? On my Android? by Anonymous Coward · · Score: 0

      No, don't kiss, suck on it - for as long as you can. It is the best bitch slap Miguel ever got.

    4. Re:Mono? On my Android? by exomondo · · Score: 2

      That's what happens when you pair it to slutty devices, like the iPhone, over Bluetooth.

      I thought the iphone was homo-phonal, you couldn't pair it to phones other than iphones...did this change?

    5. Re:Mono? On my Android? by Anonymous Coward · · Score: 0

      It's more likely than you think.

    6. Re:Mono? On my Android? by Creepy · · Score: 1

      Only a week? A girl I dated in high school was out with it for a month.

      And more on topic, I'm more interested in moonlight 4 on android, just so I can be the first to run one of my work's products on android (we require 3, but moonlight/mono is skipping 3 and going to 4).

  2. Neither by node+3 · · Score: 5, Insightful

    Will this give us the 'one language to rule them all' that Java failed to bring, or will the bad blood between the F/OSS groups and Microsoft make this a dead end?

    Neither. It will be exactly what it already is today, just one of many programming languages.

    1. Re:Neither by nicholas22 · · Score: 3, Insightful

      No, it will be less than current *platforms* (as Mono is not a language) and the reason for this is because Microsoft can wipe the floor with it at any point it feels like.

    2. Re:Neither by nicholas22 · · Score: 1

      Truth hurts?

    3. Re:Neither by the+linux+geek · · Score: 0

      The only "debatable" parts of Mono are the WinForms bits, which nobody really uses anyway. Keep on trollin' though.

    4. Re:Neither by Jorl17 · · Score: 2

      Exactly. Microsoft is Evil, remember. Wait, wasn't that a lie?

      --
      Have you heard about SoylentNews?
    5. Re:Neither by ozmanjusri · · Score: 1, Interesting

      And all future updates.

      --
      "I've got more toys than Teruhisa Kitahara."
    6. Re:Neither by bondsbw · · Score: 0

      If you develop first with Mono, there will be no worries. And if you develop first with .NET, you are free to choose not to update.

      That's only if the changes don't get published in an updated standard.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    7. Re:Neither by shmlco · · Score: 1

      "Will this give us the 'one language to rule them all' that Java failed to bring..."

      More like the one language to lose them all. Java and Flash cross-platform development have shown that you tend up with a least-common-denominator application that fails to take full advantage of any given platform, Couple that with failing to fully match a specific platform's UI and UX conventions, and you have a nice little recipe for developing a losing application.

      You're also perpetually behind the curve, OS-wise. If Apple releases iOS 5, or Google releases Android 3.1, are you good to go on launch day? Or do you need to wait for your cross-platform vendor to decide whether or not they're going to support the latest goodies?

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    8. Re:Neither by Anonymous Coward · · Score: 0

      As can still be the case with Java?

    9. Re:Neither by Gadget_Guy · · Score: 2, Insightful

      ...the reason for this is because Microsoft can wipe the floor with it at any point it feels like.

      The same FUD has been used for the last seven years, and Microsoft is still yet to "wipe the floor". As each year passes without the predicted backlash, your suggestion looks more and more like it should come with a free tinfoil hat!

      There is no indication at all that Microsoft is unhappy with Mono. In fact, Microsoft needs the Mono project to give its .NET platform legitimacy as a cross platform solution. If it tried to stop Mono then it would only serve to scare developers away from .NET completely.

    10. Re:Neither by timeOday · · Score: 3, Insightful
      Microsoft doesn't care about Mono for the same reason as Wine - because it doesn't - and never will - work well enough to be a factor either way. My two most recent encounters with it were: 1) trying to run the Netflix .net video player (doesn't work) and 2) trying to use the (only) free online tax filing site (surprise! also doesn't work).

      "But that's just because (blah blah blah)!!"

      Exactly.

    11. Re:Neither by idle12 · · Score: 1

      > Neither. It will be exactly what it already is today, just one of many programming languages.

      Yes, but /theoretically/ if I write a game in C#; then /theoretically/ I can run it on:

      Windows
      XBox360
      Linux/Mac (mono)
      iPhone/iPad
      Android/tablets.

      The only big players that are missing are:
      PS3/Wii
      "Web Games" (ie. run directly from your browser without an install) - but that can be done with Sliver Light?

      Even if it's not the full game; I can share a lot of libraries and code base.

      That's a pretty big market. If I write it in "Java" [Android isn' real Java btw]; then at best I get:

      Windows
      Linux/Mac
      Android/Tablets.
      Web Games.

      What other language can target everything that C# now can? C/C++ ... maybe... ?

      I agree that it's "just one of many programming languages"; but if you want to get a huge market share by targeting multiply platforms from "one" code base, it's a good choice to think about.

    12. Re:Neither by jrumney · · Score: 4, Insightful

      How long did it take Microsoft to start wiping the floor with their VFAT patents? Note the "at any point it feels like" in the GP's statement.

    13. Re:Neither by idle12 · · Score: 1

      oh, not that anyone cares; but C# also works on Windows 7 phones (but it's much smaller than the android & iphone markets).

    14. Re:Neither by Giometrix · · Score: 1

      I just clicked the tax site and it said I needed flash (I'm on an iPad). Is there a .net executable somewhere in there? The Netflix thing is a bummer, but it's a case of drm not being compatible with open source, as I see it. DRM sucks, but as far as I can tell, Netflix can't exist without it.

      --
      Download free e-books, lectures, and tutorials at bookgoldmine.com
    15. Re:Neither by Giometrix · · Score: 1

      I haven't looked into it in a while, but if I recall correctly, mono touch is not compatible with monodroid (though surely you can make some reusable libraries). So a mono touch app targets all of the iPhone features, while monodroid targets android features.

      --
      Download free e-books, lectures, and tutorials at bookgoldmine.com
    16. Re:Neither by Gadget_Guy · · Score: 2

      Microsoft doesn't care about Mono for the same reason as Wine - because it doesn't - and never will - work well enough to be a factor either way.

      Only if you assume that the point of Mono is to run .NET apps. True, that is what it can do to some extent, but it is also a development platform of its own (which is what TFA is all about). Developing using Mono is the best way to ensure you have a cross platform program.

      Applications developed using the base Mono libraries will work on Mono and .NET runtime. You can use libraries that will not run on Microsoft's .NET (the reverse of the problem that you had). The ultimate example is if you develop something in Mono for the Android or the iPhone then the MS CLR will not support it. But if you do decide to use a Mono library that is not supported by .NET, then you can always run it using Mono for Windows.

      In your examples, I can understand Netflix not being compatible because I don't believe Mono has implemented the DRM that Netflix uses, but there is no excuse for a tax filing application for being incompatible with both CLRs. You should complain to them, just as you would complain if someone wrote a website that only worked in Internet Explorer.

    17. Re:Neither by Gadget_Guy · · Score: 2, Insightful

      VFAT was never covered by Microsoft with a Microsoft Community Promise, have patent grants under MS-PL or Apache2 licenses, be covered by the Microsoft Open Specification Promise, or be directly specified by patent covenants. There are parts of .NET that are not explicity covered by these various patent grants, but 1) you don't have to use them and 2) (AFAIK) they are not used in these versions of Mono for Mobile phones.

      Microsoft never touted VFAT as a cross platform technology like it did with .NET. The decision to licence VFAT was made after people just started using it for themselves. On the other hand, Microsoft actively encouraged the development of other implementations of .NET. It would be a PR nightmare for them to start making legal threats against the very project that they wanted to come about.

    18. Re:Neither by Anthony+Mouse · · Score: 3, Insightful

      The Netflix thing is a bummer, but it's a case of drm not being compatible with open source, as I see it.

      It seems to me the problem is that DRM is incompatible with people owning their personal property. There is nothing stopping you from writing an open source program that encrypts movies while they're in transit over a network etc. And then people will break the DRM in two hours just like they do with the proprietary ones.

      The real incompatibility is in allowing the user to own their computer. Even if you have proprietary software, if the user can attach a debugger to it or can emulate the whole thing in software then the DRM is toast. The only way that DRM can "work" is by eliminating actual property ownership. It literally requires for us all to become renters and trespassers on what was once our own property, so that corporations can own our culture. I mean literally -- it's not an exaggeration.

      DRM sucks, but as far as I can tell, Netflix can't exist without it.

      Over-the-air broadcast TV exists without it. In higher quality than Netflix. So I'm not seeing the inherent reason why Netflix can't exist without it.

    19. Re:Neither by Anonymous Coward · · Score: 1

      Keep believing that, retard.

      As a retard I find this offensive.

    20. Re:Neither by dudpixel · · Score: 2

      No - this is wrong.

      The danger is that Microsoft can steer future versions in a path that only helps them.

      They cant take away mono or do anything to stop it in its current form. So any apps written for mono as it is today, are fine.

      The danger with mono is in betting your future on it...but the same danger exists with many other APIs too.

      --
      This seemed like a reasonable sig at the time.
    21. Re:Neither by dudpixel · · Score: 1

      but surely you would concede that mono as an API in its own right would be fine. Just another alternative way to write Android apps.

      --
      This seemed like a reasonable sig at the time.
    22. Re:Neither by Giometrix · · Score: 1

      DRM sucks, but as far as I can tell, Netflix can't exist without it.

      Over-the-air broadcast TV exists without it. In higher quality than Netflix. So I'm not seeing the inherent reason why Netflix can't exist without it.

      My assumption is that the movie studios require it, or at least require it if Netflix wants to obtain licenses at a reasonable rate. I can be wrong, but I have a strong feeling that the movie studios have a big part in this.

      --
      Download free e-books, lectures, and tutorials at bookgoldmine.com
    23. Re:Neither by hairyfeet · · Score: 1, Flamebait

      Uhhh...FUD much? Why didn't you just scream "DRM kills kittehs!" and "information wants to be free, like a bird!" while you're at it? Netflix movies are rentals and they have to have at least some token something or there would be instant copy software released an then bye bye Netflix. You also have NO choice on broadcast, and it comes with commercials, a whole shitload of them, and it is also cut. You don't get those things with Netflix.

      BTW, the reason Netflix don't (and never will) work on Linux? it requires a proprietary kernel driver and no way Linus will allow that. It works in OSX, iOS, and Windows because they have support for Janus DRM (the same one that has been around for years with no major hacks) which hooks into the kernel thus making it damned near impossible to hack without turning the data to garbage.

      I've set up several Netflix accounts for clients on their new HTPCs and the service is just wonderful IMHO. When paired with Windows 7 WMC and all the free Internet channels it makes a "one stop shop" for just about anything you want to see. Of course you are free to choose not to buy it or watch movies, that's YOUR choice but I WANT to watch movies then I should be able to choose whether or not to take DRM, yes? Hell I find Netflix less irritating than the new DVDs where you can't pass the BS in front.

      As for TFA, I guess I should have made it more clear what I was going for. With Mono on Android you can now run C# on Android, iPhone (MonoTouch), WinPhone (.NET) and on the desktop you can work in Windows (.NET) or OSX or Linux (Mono) so with C# you can pretty much cover ALL the bases. Does this have a chance of taking the "write once, run everywhere" idea of Java and making it work? Or will the bad blood between F/OSS advocates (who still scream "its a trap!" even though its been eleven years now and the patents still haven't shown up) keep it from being used?

      Who knows? I've seen people that love and those that hate C#, and a whole bunch of the "its a trap!" FUD as well. I figured with so many coders and mobile developers here at /. they might like to know there is another tool in the toolbox so to speak. Whether you choose to use it or not is up to you.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    24. Re:Neither by SanityInAnarchy · · Score: 2

      If you're going to claim Android isn't real Java, you may as well mention that Mono isn't real .NET.

      And "maybe"? Keep in mind that Mono includes C dependencies. What a platform like .NET/Java buys you is easier portability and a kinder runtime, but the only place you can run a .NET or Java app that you can't run a C app is where you're deliberately sandboxed.

      As for web stuff, the web is actually a decent platform now. I wish people would stop fucking that up with plugins. If you really want to make a browser game, make an actual browser game -- all the major mobile platforms have real browsers now, so it shouldn't be a problem.

      --
      Don't thank God, thank a doctor!
    25. Re:Neither by exomondo · · Score: 1

      No, it will be less than current *platforms* (as Mono is not a language) and the reason for this is because Microsoft can wipe the floor with it at any point it feels like.

      better quickly get back under that tin foil hat of yours.

    26. Re:Neither by jopsen · · Score: 1

      And all future updates.

      How is that different from any other platform or framework? Also you don't need to use the "debatable" parts... Assuming anybody cares, I mean they are probably only "debatable" in the US anyway...

    27. Re:Neither by exomondo · · Score: 2

      More like the one language to lose them all. Java and Flash cross-platform development have shown that you tend up with a least-common-denominator application that fails to take full advantage of any given platform, Couple that with failing to fully match a specific platform's UI and UX conventions, and you have a nice little recipe for developing a losing application.

      That's if you wrote the whole application in java. But writing a java backend with a platform-specific frontend is going to save you a hell of a lot of time porting code.

    28. Re:Neither by nicholas22 · · Score: 2
      My remark is not as trollish as you would like to portray it. See http://www.mono-project.com/Compatibility for instance.

      Everything you see there except for the C# language and a few other bits, are all *at risk*. Things like ADO.NET (used by every persistence layer such as NHibernate, Entity Framework, Linq to SQL, etc), ASP.NET, Winforms, Silverlight, Parallel frameworks, Code Contracts, WCF, WF, etc. etc. Even WPF if they ever decide to clone it.

      If Microsoft is so pro open source why don't they open up the rest of the stack (for instance WPF)?

    29. Re:Neither by gbjbaanb · · Score: 2

      Now that would be an interesting development - Mono first embracing then extending .NET (you know what follows).

    30. Re:Neither by Cerium · · Score: 1

      I'll agree that the web is significantly better than it has been in the past, but it's still not ready to drop the plugins quite yet.

      I'm currently working on a "web application" that has a minimum requirement of IE9, FF4, Chrome10, etc. You'd think that this would give me the latest the web has to offer without headaches, right? No.
      None of the browsers can agree on how to render fonts specified via @font-face (oddly enough, IE9 is the only one to get it right), the supported a/v codecs vary from browser to browser, and each browser has its own selection of the HTML5 spec implemented, so sometimes I have features available and other times I'm boned.

      Ultimately, this has forced me back to using a Flash plugin for audio support, simply because I don't feel like storing multiple copies of every sound file (or having to do other tricks to generate something each browser likes), for the fonts I'm still stuck using server side junk to generate images, and I don't even know what headaches I will have to deal with when it comes time to deal with the canvas stuff and other video-related features.

      Do I like it? Not at all, but my hands are rather tied. I can either suck it up and use commonly found and accepted plugins to solve my issues or I can spend (potentially) boatloads of time looking into ways to deal with individual browser quirks and/or missing functionality.

      The whole web-as-a-platform thing has indeed come a long way, but I don't think we're ready for a plugin-free web experience yet.

    31. Re:Neither by makomk · · Score: 1

      Applications developed using the base Mono libraries will work on Mono and .NET runtime.

      Which sounds like a nice idea, until (for example) an application you're using becomes a pain to install on Linux because one of the Mono Project additional libraries that it relies on stops working on newer Mono versions, and you have to either compile an older version or just switch to Windows and .Net to run it. (This actually happened to me. The offending library was a SQLite binding that was developed by the Mono Project and then discontinued and broken by newer Mono releases. I think I may have encountered other similar problems - in general Mono's libraries seem to run a lot better and have fewer compatibility issues under Microsoft .Net than they do under Mono itself.)

    32. Re:Neither by Anonymous Coward · · Score: 0

      Umm. Microsoft currently asserts that they have patents covering Mono. If true, then they can "take away mono" and make it illegal to run. Which would KILL any 'apps' written in mono.

      The danger with mono is that MS may decide to come after you if/when you are successful.

      If you want c#-like syntax, use vala.

    33. Re:Neither by Anonymous Coward · · Score: 0

      platform != language

      kthxbai

    34. Re:Neither by oh_my_080980980 · · Score: 1

      Except Microsoft holds patents to .NET and has not in any way provided indemnification to developers who want to develop, distribute or sell said applications.

      Microsoft has not in any way officially endorsed or recognized Mono as a legitimate .NET project.

      So go fuck yourself.

    35. Re:Neither by oh_my_080980980 · · Score: 0

      No worries? Seriously go read the license agreements. Mono is not an official Microsoft project and is not recognized as such. Microsoft did not open up .NET. Microsoft did not provide indemnification to developers using Mono.

      Go consult a lawyer moron.

    36. Re:Neither by oh_my_080980980 · · Score: 0

      LMOL....yeah Microsoft needs Mono for legitimacy? From who?? Windows developers? Linux developers? Anti-trust lawyers?

      Dude, if you are a .NET developer, you develop on Windows. No .NET developer would work on a 3rd party hack (Mono) to do .NET development. You use Windows. You have all the tools and environments you need. I know of no .NET developers who uses Mono. The only people who would use Mono would be Linux developers. If you want to push Linux as an alternative to Windows, then you would use Mono. But .NET developers, would not. Mono going away would in no way impair .NET. Again, it's about Microsoft. You're using Microsoft tools (Visual Studio), you are using Microsoft language (C#, .NET), you are using Microsoft OS (Windows).

      No one fucking cares about Mono.

      FYI .NET has been around since 2000. It has been touted as cross platform and cross language. That has not materialized in the past 10 years.

    37. Re:Neither by Anthony+Mouse · · Score: 1

      Netflix movies are rentals and they have to have at least some token something or there would be instant copy software released an then bye bye Netflix.

      Then explain broadcast TV. Shouldn't they be shutting down their transmitters, because instant copy software (e.g. MythTV) already exists?

      There is no good reason to copy a Netflix stream. If you subscribe to Netflix, you can just stream it again from Netflix for free if you want to watch it again. If you watch a lot of movies the service just doesn't cost enough to be worth trying to download a bunch of movies so you cancel, because then you would never get anything new. And nobody wants to use it to put things on The Pirate Bay because DVDs and BDs are higher quality. At best I could see if you wanted to download a movie so you could watch it on a plane or something, but it's Netflix -- just order the DVD by mail.

      Moreover, the content industries still release movies on DVD and BD even though they're both broken. If working DRM was actually a requirement then that wouldn't happen, so it obviously isn't.

      You also have NO choice on broadcast, and it comes with commercials, a whole shitload of them, and it is also cut. You don't get those things with Netflix.

      Of course they have a choice -- they could stop transmitting. Nothing stops them from replacing all broadcast TV with Netflix set top boxes that stream TV from the internet, and if DRM was half as important as you say then they would have.

      And they frequently broadcast uncut movies on TV, and anyone can strip the commercials with a DVR. So that isn't it either.

      BTW, the reason Netflix don't (and never will) work on Linux? it requires a proprietary kernel driver and no way Linus will allow that.

      It requires no such thing. If the DRM has no hardware support then there is no possible reason it can't be implemented in userspace -- the only thing the kernel can do that userspace code can't is run privileged hardware instructions. Conversely, if it requires hardware support then there is no requirement for the kernel code to be proprietary, because secret sauce is in the hardware rather than the kernel. Moreover, it works on Roku devices, which are Linux based, so clearly it isn't impossible.

      It works in OSX, iOS, and Windows because they have support for Janus DRM (the same one that has been around for years with no major hacks) which hooks into the kernel thus making it damned near impossible to hack without turning the data to garbage.

      The reason it hasn't been cracked is that nothing uses it, not because it's in the kernel. There is nothing special about kernel code -- you can run the whole OS in a VM and fool it into thinking it's running on bare metal like this. As above, nobody has a major incentive to copy Netflix streams when there are higher quality sources available. About the only good reason anybody has to break the DRM is to make Netflix work on Linux, and people are holding off on that because there is allegedly some negotiation going on between the Mono people and Microsoft to actually implement the DRM in Moonlight, which would save everyone the cat and mouse game.

    38. Re:Neither by Gadget_Guy · · Score: 3, Insightful

      LMOL....yeah Microsoft needs Mono for legitimacy? From who??

      You answered your own question later when you said:

      FYI .NET has been around since 2000. It has been touted as cross platform and cross language. That has not materialized in the past 10 years.

      The reason Microsoft needs Mono is exactly because they tout their platform as cross platform. You say that it hasn't materialized in 10 years, but here we are talking about being able to use Mono in Linux, iOS and now Android. As for cross language support, I can't see how you could possibly deny that claim!

      The rest of your post just seems to say that if you only care about running on Windows then you use .NET, but if you want Linux support then you use Mono. That doesn't actually contradict what I said. And if nobody cares about Mono, when why are you bothering to post here about it?

    39. Re:Neither by Gadget_Guy · · Score: 1

      Which sounds like a nice idea, until (for example) an application you're using becomes a pain to install on Linux because one of the Mono Project additional libraries that it relies on stops working on newer Mono versions, and you have to either compile an older version or just switch to Windows and .Net to run it.

      That seems like a valid concern. Backwards compatibility is one thing that Microsoft usually does well. Other programming languages have also had their share of orphaned libraries, but that does not excuse Mono for getting this wrong.

    40. Re:Neither by SanityInAnarchy · · Score: 1

      Ultimately, this has forced me back to using a Flash plugin for audio support, simply because I don't feel like storing multiple copies of every sound file

      ...or you could store a format that Flash can read also, and provide that in audio tag format for browsers which support it. And personally, between Flash and multiple copies, I'll take the multiple copies.

      The whole web-as-a-platform thing has indeed come a long way, but I don't think we're ready for a plugin-free web experience yet.

      The fact that others have been able to make this work tells me that maybe it's still painful to develop on, but it can still work. And the problems you've described sound fairly mild, compared to real cross-platform issues if I tried to, say, keep a common codebase between .NET/Silverlight, Mono/Moonlight, a desktop .NET client, an xbox...

      --
      Don't thank God, thank a doctor!
    41. Re:Neither by Cerium · · Score: 1

      True enough.

      ...or you could store a format that Flash can read also, and provide that in audio tag format for browsers which support it. And personally, between Flash and multiple copies, I'll take the multiple copies.

      I was purposefully vague before, so that's probably why the issues I'm having sound so trivial. So, I suppose I'll just ask that you trust me when I say these are issues which are still better handled by a plugin. (mixing, looping to specific points in a track, synchronization, etc.).

      And, I wasn't at all trying to suggest that other cross-platform issues were less significant. I'm just saying that the web isn't ready to completely shed itself of plugins. Though, I do agree that a lot of what is out there now could be done without Flash and pals.

    42. Re:Neither by SanityInAnarchy · · Score: 1

      I suppose I'll just ask that you trust me when I say these are issues which are still better handled by a plugin.

      ...no, not really, not without at least this much:

      (mixing, looping to specific points in a track, synchronization, etc.).

      Mixing works fine. Looping and synchronization, I can see, though they really shouldn't be that far off -- and I do see people doing both mixing and looping without plugins.

      the web isn't ready to completely shed itself of plugins.

      Here's where I disagree: Yes, there are things you can do with a plugin that you cannot (yet) do with straight HTML. However, as soon as you introduce that plugin, you lose a lot of the advantage of making it a web app in the first place. If that plugin is proprietary, you've also guaranteed that you are going to make things worse as long as this plugin's alive, and that whatever it's replaced with will be different enough so as to not be compatible without some sort of wrappers.

      From my perspective, if it can't be done without plugins, it's probably not worth doing on the Web in the first place. More often, it can be done without plugins, but it's harder.

      So what I'm saying here is that I don't see this as the web shedding itself of anything, I see plugins as not part of the web in the first place, and their continued attempts to encroach on that territory are damaging to what the web actually is.

      After all, replace Flash with a custom ActiveX control. Do you still feel like the Web isn't ready to shed itself of ActiveX? Or is it that ActiveX is not and never was something that belonged on the Web?

      --
      Don't thank God, thank a doctor!
    43. Re:Neither by hairyfeet · · Score: 1

      To quote Mel Brooks bullshit bullshit aaaand bullshit. Why does nobody give a shit about broadcast? because it sucks ass, that's why. That's like saying "why is nobody stealing these shit sandwiches" well because they are SHIT sandwiches, duh! And I don't know what magic land you like in but I've yet to see a broadcast movie they didn't cut to fuck. If I hear one more "eggroll" for asshole I'll bitch slap the announcer! And they don't change DVD and BD because it would break all the hardware they sold at Walmart, duh! That's why you'll be seeing Netflix like avenues getting the flix FIRST and LONGER and then, when they've made their pile o' cash, only then will you get a piece of plastic. Bet it'll suck not having Netflix then huh?

      And Roku? That thing that has hardware DRM aka DRM in a box, that thing? If Linux will agree to ONLY be allowed on DRMed hardware sure you can have it. You won't? Well too bad, you get nothing. Windows and OSX can run it without DRM hardware thanks to the bloody kernel driver you just poo pooed. So I guess it is good for something isn't it? Sure as hell just gives Linux one more reason why Joe normal won't be touching it. I mean when you have to A.-buy another OS, B.-Install a VM, and C.-run said VM, all just to watch your movies on Netflix? yeah that's a giant DO NOT WANT.

      And nothing uses it? try just about every PPV, be it on the web or elsewhere. hell Janus DRM is the only real hit they got from all that pushing WMA and WMV, and frankly it works great. Like Steam it stays out of your way, lets you see what you paid for, without having that one douchebag throw everything onto P2P three seconds after it runs and ruin it for everyone. Oh but again you wouldn't know this, because "freedom" is the freedom to do as Linus says, kinda like how even OS fricking 2 has stable drivers thanks to an ABI but dear douchebag Linus won't allow it because it would mean he couldn't teabag the kernel whenever he felt like it. What a great guy.

      And finally YOU know as well as I do why you'd have to have a proprietary DRM driver in the kernel, it is to keep the "information wants to be free! Fight the power man!" douchebag from ruining it for the rest of us. You know what would happen three days after they released the code? The "Razr1911 Netfux instant record driver" that's what and YOU KNOW THIS. We've seen it time and time again, from DeCSS to the AACS code printed into a fucking flag!

      But hey you know what? You fight the power man, you keep watching your crappy broadcast TV and thinking you've got it good, and wondering why nobody, neither in retail nor in the consumer market, will give your OS the time of day. Meanwhile I'LL be setting up nice new triples and quads, all running Windows 7, so that my customers can watch Netflix at the push of a wireless keyboard or remote. Its been 20 damned years already, you're at a lousy 1%. Time to grow up and ask yourself a simple question "What are my competitors doing right that I'm doing wrong?" (hint: its not a conspiracy).

      And then maybe you'll actually listen to the masses and actually get things they want, like Netflix and drivers that don't break like its Win98. But no, instead you'll say "eat this shit sandwich OF FREEDOM!" and then get pissy when everyone laughs and walks away. Oh and a final twist of the knife, to pop the delusions that you and so many FOSSies live under: You know why Roku and so many other pieces of hardware use Linux? It is because thanks to TiVo they can fuck you out of the code that's right! Thanks to code signing and eFuses your developers slaved away for the big nasty corps and all they got was a Goatse in the form of eFuses. Way to kill yourself for nothing developers! I'm sure the megacorps would thank you if they weren't too busy laughing at your naivete.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    44. Re:Neither by dudpixel · · Score: 1

      They also assert they have patents covering linux...

      In any case, I dont see Microsoft taking this action...but to each his own.

      Whilst I choose not to use any Microsoft APIs if I can help it, I'll not criticize others for it either.

      --
      This seemed like a reasonable sig at the time.
  3. Finally by Anonymous Coward · · Score: 0

    This is awesome. I was waiting for this a long time.

    1. Re:Finally by Locke2005 · · Score: 1, Insightful

      Miguel de Icaza, is that you? Because nobody else really gives a shit...

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
    2. Re:Finally by ArsonSmith · · Score: 1

      What does android get when kissing windows? ...

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    3. Re:Finally by KlomDark · · Score: 1

      Nah, I give a shit too. Now that the MS vs Linux battle has come to the 'like kicking a puppy' stage, there's not a whole lot of reasons to continue the hate-fest on MS. If anything, the current attitude of Apple should be hated. Hell, Apple's bigger than Microsoft in stock value now. (Although that could just be the big boys giving Jobs a magic sendoff before he kicks the bucket. Then it looks like the world is going to go back to being dominated by IBM and Java, which is just going to end up back to the original 'Evil Empire' that IBM was in the 1970s.)

      I've done Java, and I've done C#, and I gotta say the .NET framework is a lot easier to work with than the massive mess that is Java.

    4. Re:Finally by jDeepbeep · · Score: 1

      Nah. When miguel posts, he posts as miguel.

      /pedantic

      --
      Reply to That ||
  4. Finally by Alworx · · Score: 3

    Finally I can hear good quality music with just the one earbud.

    No, wait...

  5. And In Other News by MightyMartian · · Score: 5, Funny

    Reuters Minas Tirith - Mordor Inc. has announced the release of Ring of Power Open Source Version, to be released to the Free Peoples of Middle Earth. Mordor VP of Marketing, the Mouth of Sauron, has announced that the purpose of this open source version of the Ring of Power is to demonstrate Mordor's goodwill to all people.

    "We're really hoping that all those Elves and Numenoreans and Halflings take our Open Source version of the Ring of Power and use it to do all kinds of nifty things." the Mouth of Sauron said. "There has been some animosity in the past between Mordor and the rest of Middle Earth, but we're pretty keen to the idea that this is the time to put it all behind us, so we're releasing, with this commitment from Sauron himself, open source Rings of Power with no future obligations to the Dark Lord, the Nazgul or anyone else in our organization."

    When asked about previous attempts to take control of the other competing powers in Middle Earth (such as the infamous "One Ring to Rule Them All One Ring to Bind Them" proprietary patent-encumbered master Ring), the Mouth of Sauron dismissed it out of hand. "That was just business. But this is the dawning of a new age, and Mordor commits to not trying to seize control of the minds of any wielders of any open source Rings of Power... honest!"

    (With files from Rivendell Archives)

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
    1. Re:And In Other News by nicholas22 · · Score: 1

      Somebody likes his Tolkien... :)

    2. Re:And In Other News by Dracos · · Score: 1

      Aptly put, sir.

      So in two years when WP7 is still an also-ran in the mobile market, MS has another reason to trigger their patent bomb to defend .NET. Brilliant.

    3. Re:And In Other News by TrancePhreak · · Score: 2

      Wouldn't they have already done this with iPhone? Unity, which makes up a fair number of games on iPhone, uses Mono.

      --

      -]Phreak Out[-
    4. Re:And In Other News by badboy_tw2002 · · Score: 1

      Uh, the Nazgul wouldn't have been around, as they were recipients of the rings of power.

      (If I can't post a pedantic nerd post to a Lord of the Rings parody of a software announcement, where can I?)

    5. Re:And In Other News by MightyMartian · · Score: 1

      You missed another inconsistency, and that is the Mouth of Sauron, who certainly wouldn't have been around in the Second Age.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    6. Re:And In Other News by Anonymous Coward · · Score: 0

      You might say he has a real Tolkien Ring.

    7. Re:And In Other News by DrJimbo · · Score: 1

      Uh, the Nazgul wouldn't have been around, as they were recipients of the rings of power.

      Uh, those would have been proprietary Rings of Power®, just like the One Ring to Rule them All®, which was also mentioned in the press release. The good peoples of Middle Earth had become suspicious of the proprietary Rings of Power after seeing recipients turn into Nazgul and such.

      The newly released Open Source Rings of Power have all of the power and benefits of the proprietary RoPs and have the appearance of less of a downside. It is a win-win for both Sauron and for his minions.

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    8. Re:And In Other News by Anonymous Coward · · Score: 0

      The difference is that MS hasn't and will not do anything. They've let competition pass by and go this entire time (something like 6 years?). There is no reason to. You're dumb.

  6. IPhone C# by codepunk · · Score: 1

    The iPhone developer licence forbids scripting engines or Just-In-Time (JIT) compilers, which .NET needs to run code.

    Someone had better let all of the Unity IPhone developers know that they cannot use Mono C# on the iphone as it is forbidden. Really guys all of those apps you have been selling for the last two years for the IPhone is just not possible.

    --


    Got Code?
    1. Re:IPhone C# by nicholas22 · · Score: 2

      Uhm, it does, but Mono uses AOT (Ahead of Time), which is different. Wikipedia is your friend.

    2. Re:IPhone C# by Anonymous Coward · · Score: 0

      The iPhone developer licence forbids scripting engines or Just-In-Time (JIT) compilers, which .NET needs to run code.

      Someone had better let all of the Unity IPhone developers know that they cannot use Mono C# on the iphone as it is forbidden. Really guys all of those apps you have been selling for the last two years for the IPhone is just not possible.

      Simply wrong. Apple revised their license months ago, bringing Unity and other Mono-based applications into full compliance.

    3. Re:IPhone C# by Anonymous Coward · · Score: 1

      Factoid of the day: Mono does not require a JIT or an interpretor to execute .NET code!

    4. Re:IPhone C# by Anonymous Coward · · Score: 4, Informative

      Wrong.

      MonoTouch ( which is the IOS .NET development suite ) uses the Mono Full AOT feature and precompiles all the code into a static binary ( including the base class libraries ) and links in runtime stubs for GC and the likes.

      Certain features of .NET are naturally not available ( runtime code generation, features relying thereupon ) and some c# features don't work ( virtual methods in generic classes for example )

      So you end up with a fully statically linked executable with no JIT included, fully compliant with IOS licensing terms.

      Unity3D uses the same approach ( and probably shares a bit of the codebase )

    5. Re:IPhone C# by Hognoxious · · Score: 1

      Apple revised their license months ago, bringing Unity and other Mono-based applications into full compliance.

      Pray they do not revise it further.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  7. .net WebClient == no? by Anonymous Coward · · Score: 0

    .net's WebClient is hilarious in handling errors, I for one welcome the inability to find response text for problems on my Android phones as well as at work, since a fair amount of Android apps use the internet.

  8. too pricey by Anonymous Coward · · Score: 0

    How many hundreds of dollars is this thing going to cost? Bad enough to have the $400 license for iphone monotouch...

    1. Re:too pricey by Shemmie · · Score: 4, Interesting

      Exactly what I thought. So I went and looked - $99 for student (non-commercial use), $399 for basic commercial, through to $3999 for enterprise.

      Crazy. Would love to use it, won't touch it with a barge pole at that price.

    2. Re:too pricey by Shemmie · · Score: 1

      Sorry, $999 for 1 seat Enterprise, $3999 is for 5 seat Enterprise.

  9. News that matters? by MaggieL · · Score: 3, Insightful

    We already can program Android in Java (and Scala) and script it in Python, Lua, BeanShell, Perl, Tcl, JavaScript and Ruby. I hadn't noticed the multitudes crying out for Mono.

    --
    -=Maggie Leber=-
    1. Re:News that matters? by jkauzlar · · Score: 1

      +1 parent

      Will this give us the 'one language to rule them all' that Java failed to bring

      No, because Mono isn't a language. C# and F# are languages.

    2. Re:News that matters? by the+linux+geek · · Score: 4, Informative

      Everything I've seen other than Java is, at best, half-baked on Android. Scala is the closest I've seen to full-featured.

    3. Re:News that matters? by Anonymous Coward · · Score: 0

      The "multitudes" crying out for it all work for one corporation.

    4. Re:News that matters? by grubwort · · Score: 2

      Sounds like MonoTouch on the iPhone. All ticking along nicely until you hit an unexpected exception in one of the core Novell libraries. Typical open source project; push out a half baked solution and expect the "community" to fix it for you.

    5. Re:News that matters? by caywen · · Score: 3, Insightful

      I never saw multitudes cry out for C# for mobile games development, either, but Unity appears to be a very successful product. You don't need people crying out for a product to make development worthwhile.

    6. Re:News that matters? by MaggieL · · Score: 1

      The others I mentioned are scripted using the JSR-223 interface; not something you'd use for anything really deep. Scala is just Java with the compiler replaced by the same guy who more-or-less wrote the current javac, but allowing himself to define a new language with a lot of the mistakes in the design of the Java language itself mitigated. It's totally OO and totally functional at the same time, yet can use existing Java libraries with an amazing level of transparency.

      --
      -=Maggie Leber=-
    7. Re:News that matters? by wrook · · Score: 1

      Not to be negative, especially since I just started writing an Android app, but even Java seems to be half baked. I really hope that once I get used to the quirks my productivity will improve, but nothing seems to work the way I expect it too. I'm not trying to troll here, it's just that there seems to be one way that works well and about 100 other ways that may or may not work. I spend a lot of my time guessing what the one magic working way is (especially since it often isn't my first choice). I had actually thought briefly about using JRuby before I started this app and I am really, really glad I didn't. I'd be tearing my hair out by the fistful now, I'm sure. Again, not that there is anything wrong with using another language, but unless you are really familiar with the way Android is supposed to work I can imagine it being very, very difficult to determine what are quirks with Android and what are problems with the language.

    8. Re:News that matters? by ADRA · · Score: 2

      Java works fine on Dalvik, but there are performance regressions that deeply separate Dalvik from Hotspot. Sun's long and hard work over the years has produced a very well performing system that Dalvik is quite a leap from atm. The fact that they recommend avoiding virtual methods in a language with the concept deeply seeded philosophy of abstraction is disconcerting and frankly worrying. I hope that the virtual machine gets to the point where that facet and the many other performance penalizing pieces become irrelevant.

      PS: Serialization is REALLLLLLLLLLLLLLLLLLY slow.

      --
      Bye!
    9. Re:News that matters? by tepples · · Score: 1

      We already can program Android in Java (and Scala) and script it in Python, Lua, BeanShell, Perl, Tcl, JavaScript and Ruby.

      Say I'm developing a video game for Windows Phone 7 and Android. I want to use the same game logic on both platforms, with different graphics engines on top. In which language should my programmer write the game logic? Until Mono for Android, there wasn't a language that XNA and Android shared, to the best of my knowledge. No, the verifiably type-safe subset of C++/CLI supported by Windows Phone 7 is not the same thing as the standard C++ supported by Android NDK.

      And even if you claim that not even Nokia can bring enough installed base to Windows Phone 7, the above paragraph remains valid with s/Windows Phone 7/Xbox Live Indie Games/g.

  10. Re:First post! by rivetgeek · · Score: 3, Funny

    Congratulations! You won a heaping cup chock full to the brim with failure and abject destitution!

  11. Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 3, Interesting

    .NET 2 was a competitor to Java. Since then I believe the API has gone downhill so much that it really hinders development. Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?

    Like all MS software, they will blunder on thinking they still drive the entire industry, completely ignoring EVERYTHING their customers tell them and fixing only security issues. Like Windows, .NET will one day be something we look back on while shaking our heads in wonder, with the same feeling you would get watching someone dial a rotary phone.

    1. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      Yeah, I like how they went on "ignoring EVERYTHING their customers tell them and fixing only security issues" after Windows Vista came out, and then one day Windows 7 just magically popped out of nowhere.

    2. Re:Maybe if .NET 3 and 4 never happened by luder · · Score: 1

      Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?

      I'm intrigued... What data structures are you talking about? I don't remember seeing that behavior.

    3. Re:Maybe if .NET 3 and 4 never happened by sproketboy · · Score: 2

      I wish I had mod points. My guess is the microsofties here will mod you down for truth.

    4. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?

      I'm intrigued... What data structures are you talking about? I don't remember seeing that behavior.

      he doesnt understand the maybe monad. http://msdn.microsoft.com/en-us/library/2cf62fcy(v=vs.80).aspx

    5. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      One day? I develop .NET on Windows for a living - I'm already there.

    6. Re:Maybe if .NET 3 and 4 never happened by Bacon+Bits · · Score: 1

      I'm curious what your example case is. What data structure? What are you trying to do with it?

      I'm primarily a system administrator, and in the past few years I have seen nothing from Microsoft which hasn't shown a drastic increase in the amount they're listening to their customers. They've been fixing several obviously broken products and providing a lot of tools which make my job easier. The departure of Gates has been one of the best things for the company. It's slow in some areas, yes, but Microsoft is a massive company so anything they do is slow and lumbering.

      --
      The road to tyranny has always been paved with claims of necessity.
    7. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      "Like Windows, .NET will one day be something we look back on while shaking our heads in wonder, with the same feeling you would get watching someone dial a rotary phone."

      I suspect you inadvertently complimented Microsoft. The rotary phone was a huge innovation that brought a great increase in wealth to our planet. The PC using windows OS has done similar things. While not perfect, neither the rotary phone nor windows should be expected to be.

    8. Re:Maybe if .NET 3 and 4 never happened by exomondo · · Score: 1

      Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?

      No-one, what are you talking about? The only thing i can think of is the invalidoperationexceptions that are raised if you try to use the data value *without* asking if something is inside. So it sounds like you're doing it wrong.

    9. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      lol, I would never go back to .NET 2. You have to change the way you think to use the new stuff but once you wrap your head around it you will not go back. You have to think in more "functional" ways and use side effect free code to get most from it

    10. Re:Maybe if .NET 3 and 4 never happened by cyber-vandal · · Score: 1

      [Citation needed]

    11. Re:Maybe if .NET 3 and 4 never happened by cyber-vandal · · Score: 1

      What data structure(s) would those be?

    12. Re:Maybe if .NET 3 and 4 never happened by gbjbaanb · · Score: 1

      maybe he's expecting an implicit conversion to a 0 value, and use the HasValue operation if you need to know if the variable was null. I'd like that - it'd make coding easier for the majority of the time I use a nullable type and don't really care if its null or 0.

    13. Re:Maybe if .NET 3 and 4 never happened by terjeber · · Score: 1

      1984

    14. Re:Maybe if .NET 3 and 4 never happened by terjeber · · Score: 1

      Nullable data-types are a good idea. Significantly better than Java auto-boxing for example. Auto-boxing is a compile-time thing, where it should have been a VM thing. Why? Because errors in reflection when using auto-boxing can be very hard to catch. Assigning null to an Integer value in Java is not an issue. What happens if some tool, let's for example call it something silly like "Smooks", does some nifty stuff with some XML and creates objects for you. Or tries, and then assigns nulls to your int values? What happens? Impossible to track down errors is what.

      So, who comes up with a system where I can assign successfully intermix int and Integer, most of the time? The worst possible thing to deal with is stuff that works most of the time.

    15. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      Reference fields are automatically initialized to null, so why would this tool be assigning nulls in the first place? And without converting to correct the destination type nonetheless?

    16. Re:Maybe if .NET 3 and 4 never happened by majestic_twelve · · Score: 1

      Java troll be trollin'

    17. Re:Maybe if .NET 3 and 4 never happened by exomondo · · Score: 1

      maybe he's expecting an implicit conversion to a 0 value

      Then he shouldn't be doing that because in terms of nullable types 0 and null are not the same thing.

    18. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      I'll admit that C# 2.0 was basically what the 1.0 version should have been. It was simply like every other language out there, capable and nothing beyond. But they've continued to extend the language since then. They don't attempt to drive the industry (it's up to marketing to do that) but they're doing interesting stuff and are giving back to the field instead of just taking from it. You can see a comparison of C# and Java here if you want to compare the current versions.

      Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?

      Consider a dictionary of nullable ints. An exception is the only way I can know a value hasn't been assigned. Also, tryget is your friend here.

    19. Re:Maybe if .NET 3 and 4 never happened by Anonymous Coward · · Score: 0

      Not sure what you're talking about. The API has shown impressive growth and improvement. From Linq to ASP.NET MVC to dynamic support the Task Parallel Library; there really has been constant improvement and dare I say it: innovation. There have been some missteps too of course (Entity Framework and WPF come to mind). Not sure which data structure you're referring to that throws an exception on a Contains call.

  12. Implying.. by kvvbassboy · · Score: 2

    "...or will the bad blood between the F/OSS groups and Microsoft make this a dead end?"

    >>Implying that F/OSS groups are the only ones or even the majority that makes apps for android.

    I hear that .Net framework is pretty good for building good games. So it will be interesting to see what comes out of this.

  13. Re:words of wisdom, from Baraq Hussein Obama: by spun · · Score: 0

    Then: Elections have consequences! We won, get over it!

    Now: Waaah!!!

    Yeah, that's exactly what they are saying in Wisconsin today. Prosser the Tosser is out the door, Scott Walker's agenda will be killed in the courts now, the unions and working people will triumph, and the recall of the Republican senators is moving ahead full steam. The next national election will be very interesting, don't you think?

    --
    - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
  14. Great for WP7 migration! by DdJ · · Score: 4, Interesting

    It's really great that there's finally a tool to make life easier for all the developers building Windows Phone 7 apps in C# that want to move their code base to the Android platform!

    1. Re:Great for WP7 migration! by MightyMartian · · Score: 2

      And even better news that the Mono patent virus is now going to be directly infecting one of Google's flagships! Yay for Redmond and its evil little minion de Icaza.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    2. Re:Great for WP7 migration! by nicholas22 · · Score: 1

      It's great, but there aren't that many to begin with, so I hope this atleast breaks even. I like plurality in my programming life!

    3. Re:Great for WP7 migration! by Anonymous Coward · · Score: 1

      What, all 10?

    4. Re:Great for WP7 migration! by martin-boundary · · Score: 2

      What, all 10?

      Show a little respect! This is slashdot! Not everyone here knows binary!

    5. Re:Great for WP7 migration! by Anonymous Coward · · Score: 0

      And even better news that the Mono patent virus is now going to be directly infecting one of Google's flagships! Yay for Redmond and its evil little minion de Icaza.

      Yes yes, we know your anti-MS trolling is still desperately clinging to the nearly decade-old idea that MS is on the cusp of wiping out anything mono-related with its .net patents, funnily enough it's consistently been a false argument perpetuated by morons like you.

  15. Silverlight/Moonlight support on Android by Gri3v3r · · Score: 1

    What about that?

    1. Re:Silverlight/Moonlight support on Android by HalWasRight · · Score: 1

      That is my question too.

      --
      "This mission is too important to allow you to jeopardize it." -- HAL
  16. Re:First post! by DMFNR · · Score: 0

    Goddamnit, I would have got it too if I had both hands on the keyboard.

  17. Worst /. article ever? by Angst+Badger · · Score: 1

    First, this is just flamebait.

    Second, the only people who want everything to be done in one language are those clueless zealots everyone finds an excuse not to hang out with after work.

    Third, even if one language completely dominated the niche category of handheld consumer devices, it would mean nothing outside that niche.

    Slow news day?

    --
    Proud member of the Weirdo-American community.
    1. Re:Worst /. article ever? by Anonymous Coward · · Score: 0

      The story poster is a known idiot around these parts..have a look at his comment history.

    2. Re:Worst /. article ever? by hax4bux · · Score: 1

      +1 insightful

      I dunno about being the worst article (stiff competition) but spot on about "people who want everything in one language"

      I have been teaching Android development for over a year, and the biggest wankers are the ones who come to argue rather than learn.

      Real engineers don't have a problem soaking up another platform.

    3. Re:Worst /. article ever? by SplashMyBandit · · Score: 4, Insightful
      Actually, it is *terrible* design to use more than one language if you don't have to. Sure, for small, short-lived projects you can mix and match tools, but for huge, long-lived projects you need to be able to replace people quickly (with large numbers of people then staff turnover is inevitable for a multitude of reasons). Having extra languages is a negative with respect to this. This is why the relative simplicity of Java is viewed favorably in the Enterprise and more complex and obscure alternatives (which may actually be better fits for the purpose) are avoided.

      With regard to your "find an excuse to not hang out with after work" comment. Actually, it are pseudo-academic language snobs who are avoided. The kind who love adding layer upon layer of complexity (including switching languages and tools all over the place), and take pride in their l337 skills for doing this. They can be great developers but are shitty *designers* (too bad they're usually so clueless at design they never even see or consider this aspect). Remember, great design is about *removing* stuff. As Einstein said, "As simple as possible, but no simpler" [note: this is actually misquote of what he actually said, but it is commonly enough used and conveys the same meaning in fewer words]. That means *fewer* languages, not more, should be preferred.

    4. Re:Worst /. article ever? by SplashMyBandit · · Score: 1

      Huh? how do the "arguers" have anything to do with "one language" ? (aside from a commonly used argument). Having a single language that can meet your development needs is a Good Thing (tm). Remember the K.I.S.S. principle? Sounds like you are indeed a teacher of "development" but not a teacher of "design", and good design [rarely taught or learned, especially not in software] aims to simplify where possible - which means "one language" is a good design goal (and it always indicates poor design in an API if a single language cannot be used to solve most common problems).

    5. Re:Worst /. article ever? by Draek · · Score: 1

      The "one language to rule them all" bit isn't about having everyone use the same language, but about having a language supported on every platform. Java, AFAIK, isn't supported on iOS which is why it's considered a "failure" in that respect, and obviously nobody outside Apple uses ObjC for anything serious so that one's dead as well.

      --
      No problem is insoluble in all conceivable circumstances.
    6. Re:Worst /. article ever? by sproketboy · · Score: 1

      Yes exactly. .NET is a foundation fail.

    7. Re:Worst /. article ever? by idle12 · · Score: 1

      Well, if you already have a code base; then theoretically porting it from C# on iPhone to C# on Android would be easier than say Objective C->Fake Java. It opens that market for you without much effort which is "near" free money.

      I maintain a few Java apps that run on Win/Linux/Mac. It was pretty easy to port it over to Android. It's nice to be able to target a few extra platforms for cheap.

      Linux is only 2% of our user base. We get that for a few extra hours of dev and some QA time from our Java/OpenGL games. We also have some games in C++/DirectX but cost wise it won't make sense to port those over since the users aren't enough to justify spending the dev time to port it (or even wine it).

    8. Re:Worst /. article ever? by Anonymous Coward · · Score: 0

      I would argue that there is an advantage to using a scripting language (Python/Perl/Ruby/Powershell/etc.) for some tasks over a compiled language like C#/Java/C/C++/etc. especially for code generation. Still choosing one full compiled language and one scripting language is better than choosing 20. Just using one compiled language quite often a lot of stuff that can be automated/built won't be because it will take too long while with a scripting language often much more will be done.

    9. Re:Worst /. article ever? by MightyYar · · Score: 1

      Actually, it is *terrible* design to use more than one language if you don't have to

      I think there are exceptions. Python with some C for the fast bits can be quite compelling.

      And I don't know if it counts, but mixing C and C derivatives like C++ or Objective C is pretty common.

      I think it depends on your requirements. Obviously it is ideal to KISS, but if writing most of the code in Python saves you months or even just weeks of coding time, then it is hard to say that a straight-C implementation is "better".

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    10. Re:Worst /. article ever? by ADRA · · Score: 1

      Which is a good reason that C/Python have almost no adoption outside of the OSS world. I've worked in enterprise for long enough to know that there's no way that I'd let half the developers I've worked with use C as their standard language. Does that mean that C#/Java are better languages because of it? Yes. If I can cut out the ugly overly open languages that make some much more effective but most of the others incompetent or highly ineffective, then I choose no.

      When is C appropriate? We all know systems development will remain solidly C based for quite a while. If Google (or the like) could get a language like go to do 100% conversion of the Linux kernel, I think that would persuade a large number of forces to take a serious look at the language. I haven't more because I don't care about program for bits, bytes or pointers anymore. Better yet, if you could compile the Linux kernel using a statically linked language and have it optimized it to levels within deviation of the GCC's efficiency, we'd be looking at the death of C. Oh, and of course we'd need to have the compiler compile itself as a minimum =) Of course I don't see either scenario happening for quite a while, so no need to worry.

      --
      Bye!
    11. Re:Worst /. article ever? by SplashMyBandit · · Score: 1

      Absolutely correct analysis correlating with my experience. It's very hard making a huge program out of C (too many low level details to keep track of, and poor support for mixing multi-threading and memory management). IMHO the 'open' languages you mention are good for small scale stuff but also hard to scale to the huge (the compiler and tools just can't help you get so many things right *before* you compile and before you run). It's unfortunate that fans of languages of Python think that because Python is quick to develop small applications in then it follows that it would be similarly quick to develop a large application in (which is false, since the debugging effort would increase dramatically). The apparent relative 'slowness' of developing in statically-typed languages like C# or Java is mostly because they are more strict, which allows the compiler and tools to help out during development (incremental compilation and error detection). After all, if your program doesn't have to work correctly every time then your development time can be zero and languages like Python or Lua are good choices :)

    12. Re:Worst /. article ever? by Anonymous Coward · · Score: 0

      You got it wrong. Java is *quite* complex. Other languages, like ruby, are much simpler, but also less flexible. The problem is that they are aimed at the same niche: general programming. Who needs seven different languages to do the same? More special purpose languages (aka Domain Specific Languages) is what you need, those that allow you to express a complex problem in a few lines of code, providing only the relevant details, and abstracting out what's not.
      The reason for Entreprise favoring Java is that it comes with great tools, thus lots of cheap kids can do a decent job with little or no training. The *cheap* part is what Entreprise likes, indeed.

    13. Re:Worst /. article ever? by MightyYar · · Score: 1

      There are many documented large non-open projects that use Python. It is nowhere nearly as wide-spread as Java or C#, but it also has no marketing department.

      I'm not going to say it is "better" than C# or Java, because those are both awesome tools. I was merely pointing to Python + C code as an example of where you could benefit from mixing languages when you need more speed than Python (or for that matter Java or C#) can give you alone. Certainly you don't want to write an entire application in C just because you want the speed of C in some areas?

      Another example, if you prefer C#, would be to call a custom DLL that is written in C/C++ from C#. This can be done in a clean, maintainable way. There are probably whole books on marshaling.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    14. Re:Worst /. article ever? by SplashMyBandit · · Score: 1

      My point was that Python is not used to build *huge* applications, simply because it doesn't easily scale that far (humans need help to gr0k the massive). Oh, you don't need C to make Java faster, since except in a few parts of the standard libraries the JVM is generally faster than C (if you want I can give you a link to the report when INRIA, the French scientific supercomputing folks, did tests) and is approaching FORTRAN for speed. With Java you only really needed C/C++ to do JNI native library integration, but with the third-party JNA library don't even need to do that anymore.

    15. Re:Worst /. article ever? by MightyYar · · Score: 1

      Even if you don't need C from Java to go faster, sometimes you might want to talk to hardware or leverage an existing library that is already implemented. My point is that mixing languages can make sense... I'm certainly not qualified to compare the scalability of the various programming platforms that are out there.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    16. Re:Worst /. article ever? by SplashMyBandit · · Score: 1

      I have used C and C++ multiple times to make JNI interfaces with a *lot* of hardware (US $30,000 scientific cameras; all sorts of electronics; closed-source native driver libraries, etc etc). These days JNA can pretty much do the integration I need - meaning, using Java means mixed languages are less necessary than they once were, and Java works just about everywhere (except when deliberately excluded, iOS).

      With regard to scalability. I recently did a long contract for a global system for a very large US software company who I cannot yet name (they have hosted services as well as desktop stuff). The scale was massive (so called 'Internet scale'). Here we used Java (mostly intended for Linux given the economics of deploying on thousands of servers). The reasons we used Java were the reason I outlined in my original post: strictness of the language means a large team can work on it and comprehend it and the tools give a lot of support to find obscure bugs (at this scale a one-in-a-million threading issue will swamp tech support with hundreds of occurrences per day). Mixing languages in this environment would be a disaster as would dynamic typed languages. Hence, my comments were made because I am experienced with this stuff.

      Thanks for taking the time to make your points known, listen, and discuss rationally - wish it was always like that on Slashdot :)

    17. Re:Worst /. article ever? by MightyYar · · Score: 1

      Thanks for taking the time to make your points known, listen, and discuss rationally - wish it was always like that on Slashdot :)

      LOL, yeah right back atcha.

      I work in real-time stuff (factory automation). We just started a brand-new rewrite of our million+ line codebase that was in C, and we chose C++. Even then, performance is still a major concern. I guess it is conceivable that Java could have been used for the underlying logic and the real-time stuff could be moved off to a separate processor running C, but now you are adding hardware just to discard the old codebase. I know there are Java real-time setups now, but I don't think they are as mature as VxWorks (though there are some that will run on top of vxWorks.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  18. That fella Miguel... by bogaboga · · Score: 0

    ...I just wanted to say..."He's one hell of a programmer..." He definitely has lots of ambition. Google should pull him into Android programming for his [incredible] talent will be a plus to Android development.

  19. Kinda pricey... by MaggieL · · Score: 5, Informative

    This just in: "Mono for Android includes the core Mono runtime, bindings for native Android APIs, a Visual Studio 2010 plug-in for developing and testing Android applications, and a software development kit (SDK). The enterprise edition costs $999 (£613) per developer per year, including maintenance and updates. A five-developer enterprise licence costs $3,999 per year, and a professional edition costs £399 per developer per year."

    http://www.zdnet.co.uk/blogs/communication-breakdown-10000030/novell-releases-mono-for-android-toolset-10022167/?tag=mncol;txt

    --
    -=Maggie Leber=-
    1. Re:Kinda pricey... by swabeui · · Score: 1

      A few years ago I would have agreed 100%. Running a SW department with people with all different strengths I'd be fine to pay it. If I needed Android development I would have two choices. Hire someone new (way costly) or have a C# developer pick it up. My guys are sharp and could do it but the learning time needed would be far more than a grand. Assuming it worked well I can see it saving money for a lot of C# dev houses that have increased demand for Android/iOS apps.

    2. Re:Kinda pricey... by vgerclover · · Score: 1

      So your guys are sharp, but they can't use C#'s older cousin Java? They aren't sharp, they are #.

    3. Re:Kinda pricey... by tomhudson · · Score: 1

      If you remember your music C# is also D flat (or D-), which is what I grade Mono as, for the simple reason that you don't need it for Android.

    4. Re:Kinda pricey... by gbjbaanb · · Score: 1

      the learning time needed is mainly down to the platform, the API, the "way things are done" on the new platform. The language ... almost an irrelevance.

      The disadvantage, huge disadvantage, of coding everything in the language that no-one else uses for this platform's development is that you cannot find too many examples, sample code, and tutorials to help your devs get to speed with the new platform. That will cost you much, much more in the long run than you save in the short-term by trying to re-use your existing skills.

      Now, I can see it being useful for C# shops that want a quick n' not-so-good Android port of their app.

    5. Re:Kinda pricey... by tepples · · Score: 1

      you don't need it for Android.

      But you do need it for Windows Phone 7 and Xbox Live Indie Games. If you want your game's logic to be portable across multiple platforms, even with a different graphics engine on top, the platforms have to have a language in common.

    6. Re:Kinda pricey... by tomhudson · · Score: 1

      But Windows Phone 7 is stillborn, and it's doubtful that it will ever break into the double digits, so why bother?

      As for the Xbox, that's a different market, different display and controls, etc. Porting those games to a phone is still going to require a major rewrite anyways, so again, why bother?

      For man, Mono is just a "solution" looking for a problem; for others, it is a problem all by itself. I'm not a fan of Java by any means, but it gets the job done, and eclipse is a decent development environment, even on comparatively old machines, provided you have a big enough display.

    7. Re:Kinda pricey... by Alarash · · Score: 1

      You don't have to buy any of that to use Mono. You can use their Migration Tool (which is free, just a little less practical because it's not integrated in Visual Studio). I'm developing in ASP.NET MVC 3/C# 4.0, my web server is lighttpd w/ Mono. I use Visual Studio Express which is free (and a kick ass IDE at that) as well. I use Postgresql which is obviously free too. So I'm using .NET 4.0 for web, and that doesn't cost me a dime and nobody can sue me. I fail to see what is evil in this scheme. I'm not more pro-Microsoft or anti-Microsoft than the average people, because I went past my hate for MS and started looking more objectively to what they do. It's not perfect (not one project on earth qualifies for perfection) but it sure isn't worse than Java or PHP or Ruby or whatever your favorite language for websites is.

    8. Re:Kinda pricey... by MaggieL · · Score: 1

      What does any of that have to do with Android?

      --
      -=Maggie Leber=-
  20. This will not rule the world by prefec2 · · Score: 3, Insightful

    First, it is mono. Beside any technical argument. There are a lot of people who do not like mono, because it is an incarnation of evil (alias MS). I am not saying that it is, but many people feel that way. So this is definitely one obstacle. Second, Android and iOS are different enough to be different on the low level aka programming language level, which will result either in compatibility libraries which are wrappers and resemble at some point internal DSLs. And they result in another abstraction layer which costs memory and CPU power. When you used an iPhone 3G/3GS you already find your phone to slow. So why torture yourself with slow software. And fourth, there are other cross platform approaches which use external DSLs which do not introduce another layer of abstraction at runtime, only on built time. For example: http://code.google.com/p/applause/

    1. Re:This will not rule the world by Anonymous Coward · · Score: 0

      Actually this won't even annoy the world a little. The vast legions of .NET developers are used to free tools that run on cheap hardware. Make them pay a subscription and the use Mac hardware and all you're doing is creating yet another fully bastardized solution.

    2. Re:This will not rule the world by Bacon+Bits · · Score: 2

      First, it is mono. Beside any technical argument. There are a lot of people who do not like mono, because it is an incarnation of evil (alias MS). I am not saying that it is, but many people feel that way.

      Yeah, but look at your alternatives. You can use Mono, aka .NET, aka Microsoft. Or you can use Java, aka Sun, aka Oracle, aka plaintiff in litigation against Google over Java in Android.

      Giant douche or turd sandwich?

      --
      The road to tyranny has always been paved with claims of necessity.
    3. Re:This will not rule the world by KingMotley · · Score: 1

      You are confusing a language with a UI (or hardware) library. Sort of. It's a bit more complicated than that, but I'll leave it as that to not further confuse you.

      In actuality, .NET, mono, monotouch, and monodroid are a collection of base class libraries, interpreters (or compilers), with each diverging with their own separate UI/hardware libraries. Additionally, the later two (or three) are compiled, with no "additional abstraction at runtime".

    4. Re:This will not rule the world by chammy · · Score: 1

      Or you could always use the NDK and code in C/C++. Only minimal bits have to be in Java to interface with the rest of Android.

  21. lol, C# by Anonymous Coward · · Score: 0

    nuff said

  22. pardon me... by Anonymous Coward · · Score: 1

    I just threw up in my mouth a little.

  23. "which allows c# development on iOS" by Anonymous Coward · · Score: 0

    well, to be precise, it allows c# development _for_ iOS. you'd have to be insane to write code using your iphone

  24. I admit it, I like C# by Anonymous Coward · · Score: 0

    Man, I've programmed in everything on custom embedded to web apps ... and I have a confession ... I really like C#.
    Of course I can nit-pick, but it is really the first language where the syntax and debugging does not hinder me.

  25. Mono for Android! by Locke2005 · · Score: 3, Funny

    For all those developers that really want to combine all the disadvantages of programming for Android with all the disadvantages of using a Microsoft-controlled API!

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
    1. Re:Mono for Android! by Mr2001 · · Score: 0

      Microsoft-controlled API

      You misspelled "ECMA-standardized API". HTH!

      --
      Visual IRC: Fast. Powerful. Free.
    2. Re:Mono for Android! by SplashMyBandit · · Score: 3, Informative

      The C# language is/was ECMA-standardized. The libraries (eg. the "API") most certainly is not. Even disgregarding the legal aspects, the fact of the matter is that the only complete implementation of the .NET stack is Microsoft's. Mono is missing many major components, as detailed in their page:
      http://www.mono-project.com/Compatibility

    3. Re:Mono for Android! by FreelanceWizard · · Score: 1

      I'm not sure how one could look at the chart at the provided link and take away that Mono is missing "many" major components.

      With the exceptions of the limited implementation of WCF, which ends up forcing you to use painful (albeit well-documented) approaches for web service access, and WPF, for which you can use the workaround of using any other windowing library with a C# binding, most of what's missing is stuff few people would miss anyway. For example, the Entity Framework is a rather clunky and immature ORM; you can do better by rolling your own, avoiding ORM entirely, or using one of the many available .NET ORM libraries. WF is rather specific to particular business applications and, in my experience, sees relatively little practical use outside of the BizTalk and SharePoint communities. System.EnterpriseServices is of questionable utility due to its reliance on COM+; you can emulate most of what it does by choosing your hosting environment carefully and using System.Transactions.

      Mono current implements all of the cool features of .NET (again, WPF and WCF notwithstanding), such as (P)LINQ, ASP.NET MVC, and C# through version 4.0, including lambda expressions (the new hotness).

      Really, Mono is pretty compatible and implements most of what a developer needs unless they're doing particular types of deep magic using WCF, such as implementing request interceptors and custom authentication mechanisms. Personally, I think it's unfortunate they won't implement WPF, but I can't really fault their decision; Gtk# is an entirely reasonable alternative and more familiar for the non-Windows crowd at which Mono's aimed.

      --
      The Freelance Wizard
    4. Re:Mono for Android! by SplashMyBandit · · Score: 1

      "Gtk# is an entirely reasonable alternative and more familiar for the non-Windows crowd at which Mono's aimed."
      While I understand this position, it is mostly a 'fail' for the Windows C# crowd. Having a non-portable stack is a big issue. Non-portable (ie. non-standardized) libraries means you can't trust whether it is going to be on your *customers* chosen platform or not (and big customers get to chose the platform, not the developer). Trying to sell a Gtk# solution would work in some places, but there are plenty of customers who would reject it out of hand. This means Mono probably will get limited traction in such (enterprise) spaces, especially when Java does the same thing but far more portably (and the niceness of C# syntax is never a customer concern, and any productivity gains are marginal at best - so I doubt real customers would see many upsides to having Mono-based solutions even if developers do).

      Those of us that did C and C++ for two (approaching three) decades want to go back to the bad old days of balkanized solution spaces (eg. juggle both WinForms for Windows, Gtk# for Linux, Cocoa bindings for Mac etc etc - possible to do but just a PITA). We're past the point of finding it 'fun' to re-invent solutions for every platform simply because of different/non-portable libraries, and it certainly makes no commercial sense to do this either. Hence a lot of developers have chosen tech where they don't have to do this.


      If C# libraries were as portable as Java and supported by the vendor (eg. Microsoft) then C# would be a rational choice and would dominate development - C# has certainly matured and have plenty of time to achieve this. However the Tiobe Index figures show that C# adoption is not growing very rapidly (certainly not as much as its proponents would like). If C# library portability was a design goal then C# would make sense for development on phones and pads (the topic of this Slashdot article). Even Java falls short in this space (although, as Android gets more powerful I expect eventually to be able to run Java SE libraries on Android - I've deployed Java SE applications to far more constrained embedded/Single-board systems than what is available today to host Android). So, C# may be nice but it is never going to be of much interest to Android (and Big Enterprise) developers.

    5. Re:Mono for Android! by spongman · · Score: 1

      The libraries (eg. the "API") most certainly is not

      actually, the base libraries are in partition IV of the ECMA/ISO spec.

  26. The nebulous danger by steveha · · Score: 3, Insightful

    As I understand it, here is the chief complaint that people have about Mono: Microsoft could have some sort of patents that could apply to Mono; and Microsoft could in the future use these patents to do something bad.

    I have never seen any specific examples given, it's just a general "there could be some patents" argument. In fact, I believe the theory is that these could be "submarine" patents, not known now but lurking invisibly.

    Here's a specific example. This is a long essay about this very issue. What is the danger if we use Mono? "[C#] was developed inside Microsoft, so it's likely they have many patents to cover different aspects of its implementation." Got that? "it's likely" Microsoft has "many patents". Citation needed.

    This is the 21st Century, and patents are not only public, there are patent search engines. Where are the specific examples?

    The situation is even crazier due to the passage of time. Microsoft introduced .NET in the year 2000. It is now the year 2011. Patents in the USA today have a term of 20 years. Presumably these submarine patents were not filed the same year as .NET was introduced; that would be far too obvious... they were probably filed a year or two ahead of time. So presumably these patents have a maximum life of under 9 years, and probably under 7 years.

    In the past 11 or 12 years, nobody has noticed these deadly patents, lurking. But wait: these could be true "submarine" patents, where the patent was filed but not granted yet, and Microsoft is using sleazy tricks to extend the filing period and delay granting the patents. This implies that the patent must have been filed before 1995, when the US patent system was changed (patent term went from "17 years after patent granted" to "20 years after patent filed", specifically to fix the problem of submarine patents). Thus, a true "submarine" patent would have to have been kept going via sleazy tricks for over 16 years now, and nobody has noticed it yet.

    So, if I understand correctly, we shouldn't use Mono because it could be a trap. Microsoft could have patents nobody has noticed for a dozen years that will expire within the next nine years that could apply to Mono. Or else they could have pending patent applications that have been pending for over 16 years without anybody noticing; those would apply for 17 years after the patent grant finally occurs in the future.

    And if the above turns out to be true, and you wrote a program in C#, what would Microsoft's remedy be? Would you be forced to pay them huge sums of money? Would you be forced to give ownership of your source code to Microsoft? Not likely, and anybody who claims it is likely needs to provide legal precedents showing such a remedy in a similar case. No, the only realistic remedy would be that you would have to choose between buying some sort of licensed version of Mono (to comply with the patent licensing terms), or stop using Mono.

    And the obvious exit strategy is to rewrite your C# app in Java. That would be a pain, granted, but hardly the end of the world.

    And that is even assuming that Microsoft was successful in asserting these hidden patents. After offering C# up as a free standard, and not taking any action for a dozen years, to suddenly assert hidden patents would leave Microsoft wide open to the "unclean hands" legal doctrine. It's hard for me to imagine Microsoft prevailing in this.

    And nobody has yet proposed a motive why Microsoft should do this. How does Microsoft gain by backstabbing the C# community? In the near term they could gain some patent licensing fees, but in the long term they would be alienating people they have been trying to woo. How likely is this, really?

    So, in conclusion: because of this nebulously scary potential situation with possible unknown Microsoft patents, Mono and C# are

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
    1. Re:The nebulous danger by Anonymous Coward · · Score: 1

      Microsoft has been threatening patents on Linux for 15 years, should we stop using Linux? No.

      The fact that Microsoft has failed to reveal any patents means that we should consider all or most of their patent strategy to be expertly-made FUD.

    2. Re:The nebulous danger by symbolset · · Score: 2

      Using any of their things, no matter how trivial or open, is just biting their hook. Once you're on the hook they'll let you swim around quite a while before they reel you in, in the hope you'll bring more friends. Just don't do it. You wouldn't drink from the outlet of a sewage treatment plant, would you? Clean water falls from the sky, and great toolchains from less revolting sources are available.

      --
      Help stamp out iliturcy.
    3. Re:The nebulous danger by makomk · · Score: 2

      As I understand it, here is the chief complaint that people have about Mono: Microsoft could have some sort of patents that could apply to Mono; and Microsoft could in the future use these patents to do something bad.

      I have never seen any specific examples given, it's just a general "there could be some patents" argument. In fact, I believe the theory is that these could be "submarine" patents, not known now but lurking invisibly.

      That's mostly because no-one wants to go looking, not because they're hard to find. For example there's US patent 6951022 which covers using .Net delegates to dispatch events that have two arguments, one identifying the event source and another that's a structure containing the event arguments. Seems oddly specific, but GTK.Net does exactly this, and it's likely that many other .Net and Mono-based apps also do so because they're following Microsoft's coding standards. That's enough to take out pretty much every GUI desktop app based on Mono by itself. What's more, the patent is specific enough to make finding prior art infeasible, and because the infringement of the patent is in code outside the core .Net stuff none of Microsft's patent promises apply (though those are fairly worthless anyway).

      Remember that what I've described is just one single patent trap. A very clever patent trap, true, but there's nothing to stop Microsoft having a whole bunch of other patents out there similarly designed to entrap anyone that uses .Net features in applications and libraries.

    4. Re:The nebulous danger by makomk · · Score: 1

      That should of course be Gtk# not GTK.Net. Bleh, it's getting late.

    5. Re:The nebulous danger by steveha · · Score: 1

      The limits of my C# knowledge stand revealed. I do not know very much about this stuff, at all.

      Are you saying that Mono is fundamentally broken, because this feature is essential to Mono? Would it be possible to rewrite Mono to not use this feature, if Microsoft ever started asserting this patent?

      And, while I am not a patent lawyer, isn't it generally true that the more specific the patent, the easier it is to work around the patent?

      Also, this patent expires in 2021, so it must have been filed in 2001, which is after C# and .NET were introduced. Thus, while I am not an expert in this stuff, I think this cannot by itself destroy Mono as a platform.

      Or, would you say that this patented technique is firmly embedded in current practice and in practice not possible to remove?

      In any event, I thank you for providing a specific example, the first I have seen in the years I have been reading about C# and Mono.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    6. Re:The nebulous danger by Kjella · · Score: 1

      It's one issue but not the only one - and could be well explained by mono not being very popular, it doesn't matter how much time has passed if there's not enough in the trap to be worth springing it. Another issue is that almost everyone writes for Microsoft's CLR. No matter if it's spec ambiguities, bugs in Microsoft's implementation or bugs in Mono's implementation the most common answer you'll get if it works on their version and not mono will be "dunno, use Windows" as if mono is something akin to WINE. Just like if Linux were to ditch OpenGL for DirectX, or at least some "almost-but-not-quite" standard similar to it.

      --
      Live today, because you never know what tomorrow brings
    7. Re:The nebulous danger by zzatz · · Score: 4, Insightful

      Microsoft could end the patent issue once and for all by granting a royalty-free license for any and all patents needed to implement a C# runtime. They have not done so. That suggests that they reserve the right to use those patents against any competitor who becomes a large enough threat, or any one else with deep pockets.

      IBM has more patents than anyone else, yet they give patent grants in situations like this. Many companies do. Sometimes growing the market by making standards more affordable is better than protecting your share of a smaller market. Microsoft's actions speak louder than their words, and their actions come down on the side of reserving the option of shutting down the use of C# in ways that Microsoft doesn't like. You think that it's silly to fear that Microsoft would do that, I think it's silly for Microsoft to fear that someone might someday use Microsoft's C# patents to harm Microsoft.

    8. Re:The nebulous danger by Anonymous Coward · · Score: 0

      Another issue is that almost everyone writes for Microsoft's CLR.

      "almost everyone"? Citation needed. How do you know that? Where are you getting this information?

      What about Beagle, Tomboy, F-spot, GNOME Do, and Banshee? They get lots of community hate because they were written in Mono, but they were always Linux native apps; they written on Mono in the first place.

    9. Re:The nebulous danger by Bacon+Bits · · Score: 1

      Honestly, in this case the patent problem is wholly beside the point. You could choose Mono and carry an extremely low risk of patent litigation (this kit is produced by Novell which has a good relationship with Microsoft including patent detente) or choose Java... which is currently the topic of ongoing patent litigation between Google and Oracle.

      Gee, which of these two is really less appealing?

      --
      The road to tyranny has always been paved with claims of necessity.
    10. Re:The nebulous danger by Anonymous Coward · · Score: 0

      or choose Java... which is currently the topic of ongoing patent litigation between Google and Oracle.

      You can use the GPL Java, or you can license Java from Oracle for money, and either one will not put you in a patent suit.

      Or, you can write your own VM that is very much like Java; then Oracle will add you to the lawsuit.

      Unless you accidentally write and release your own VM, Java is a safe bet. I don't see Amazon abandoning Java, or other big companies either.

    11. Re:The nebulous danger by devent · · Score: 1

      I don't think the thread of software patents have any stand. I'm sure there are a lot software patents for C#/.NET that Microsoft holds, but who are they going to sue?

      They can't sue Google, because Google don't sell Android phones. They can sue all the others, like Motorola, etc. (what they already do without Mono or C#). But they can't sue the others because of .NET patents because they won't deliver Mono with Android anyway.

      Theoretically they can go after the developers that uses Mono on Android, but I think the risk is minimal. But if Microsoft really do it, it will be suicide for any open source efforts that Microsoft have done in the past and in the future. Nobody will ever again trust Microsoft in anything they are opening as open source, which is quite a lot from a company with in the past stated "Open source is a cancer".

      In my opinion, C# is just an awful language. Which is a mix of Java, C++, it's just a mishmash of language features, which many language features just don't make any sense and are just redundant. For example, the distinction between struct and class. Delegates are not type safe. The properties. Operator overloading. No checked exceptions. Two collections frameworks, one without generics, one with generics.

      It's just my opinion after programming in C++ for 4 years, Java for 6 years, and starting with C# back in C# 2.0, and recently with C# 3.0 making a web project in ASP.NET.

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    12. Re:The nebulous danger by spongman · · Score: 1

      well, there's this and this.

    13. Re:The nebulous danger by nicholas22 · · Score: 1

      Just one word: VFAT

    14. Re:The nebulous danger by jabjoe · · Score: 1

      It's not just a patent problem. It's the old chasing tail lights problem. MS have a long history of encouraging people to commit to follow them, and then swerving like mad to loose them. Throwing patent rocks out the back is just one dirty trick that they have used in the past. It's all well documented, you won't have to look hard. One of the better sources is as always Groklaw.

    15. Re:The nebulous danger by makomk · · Score: 1

      Are you saying that Mono is fundamentally broken, because this feature is essential to Mono? Would it be possible to rewrite Mono to not use this feature, if Microsoft ever started asserting this patent?

      The core of Mono itself probably isn't immediately affected by the patent, because Microsoft have promised not to sue over their patents required to implement the standardized core parts of C# and .Net - though that has some major caveats and doesn't stop them selling it to a patent troll that sues Mono on their behalf. What is affected is Gtk# and every app that uses it. It's impossible to fix this issue without changing every Gtk# application too because it would mean modifying the public API in a way that wasn't backwards compatible.

      Also note that even converting the affected applications to C++ and dropping Mono entirely may not be enough in all cases, depending on how much they rely on C#-style events internally and how this code is converted over!

      And, while I am not a patent lawyer, isn't it generally true that the more specific the patent, the easier it is to work around the patent?

      I'm not a patent lawyer either, but normally that would be the case. The trouble is that since Microsoft both designed.Net and filed the patent, the specific details are designed to nicely match what you have to do to implement the .Net framework's events and delegates feature. About the only way around it is for every piece of code using them to avoid having their events take a sender argument together with a structure-of-arguments argument, I can't see any way to work around this within Mono itself. This is why people say things like "[C#] was developed inside Microsoft, so it's likely they have many patents to cover different aspects of its implementation."; it's only easy to work around highly specific patents when you don't have to comply with a standard designed to funnel you into infringing on them.

    16. Re:The nebulous danger by makomk · · Score: 1

      Another issue is that almost everyone writes for Microsoft's CLR. No matter if it's spec ambiguities, bugs in Microsoft's implementation or bugs in Mono's implementation the most common answer you'll get if it works on their version and not mono will be "dunno, use Windows" as if mono is something akin to WINE.

      Not just that, but the problems caused by Mono behaving differently can be hard to track down. For example, I occasionally use OpenSim which is written in C# and nominally targetted at both Mono and .Net. For ages, it leaked truly massive amounts of memory on Mono to the point of being unusable; turns out that certain objects that can be garbage-collected in .Net have to be tracked and freed manually in Mono. (Miguel de Icaza even heard about the complaining; his response was to run the server for an hour or so without actually using it and insist there was no problem and that all the complains were FUD. The issue was only triggered if you actually used the server for a period of time, though it did fall over in under less than an hour under heavy use.)

    17. Re:The nebulous danger by Anonymous Coward · · Score: 0

      But you still don't answer what I think is the key point: What's the advantage to Microsoft in asserting these patents and suing people who are helping to spread the use of C#? To me it looks as if it would be counter-intuitive and suicidal to start going after everyone over Mono. It would kill the language everywhere, including Windows.

      In the end I think the patent you mention plus any others that might be "lurking" out there are just another part of a defensive portfolio. Unfortunately if you don't build one these days, you're going to eventually be sued out of business.

    18. Re:The nebulous danger by Just+Some+Guy · · Score: 1

      But you still don't answer what I think is the key point: What's the advantage to Microsoft in asserting these patents and suing people who are helping to spread the use of C#? To me it looks as if it would be counter-intuitive and suicidal to start going after everyone over Mono. It would kill the language everywhere, including Windows.

      Imagine that Microsoft magically gained low-level, impossible-to-work-around patents on the underpinnings of C. Imagine their delight to be able to say "we're licensing our C patents for only $10,000 per non-Windows desktop and $50,000 per non-Window server! Oh, you Windows users can keep using C for free." In one stroke, there goes Linux, OS X, Solaris, iOS, and every other non-Windows system in the backwards parts of the world that recognize software patents.

      Microsoft has refused to declare that they won't do this to Mono users. Wouldn't it suck if Mono were widely adopted for Linux development, only to have a future Microsoft decide one day that they wanted to take their toys and go home?

      That is what a lot of Linux users worry about.

      --
      Dewey, what part of this looks like authorities should be involved?
    19. Re:The nebulous danger by tepples · · Score: 1

      Clean water falls from the sky

      and great toolchains from less revolting sources are available

      If you want your program to be portable between Android phones and a set-top video game player, you have to deal with Microsoft. Set-top PCs are so uncommon they might as well not exist, and Sony and Nintendo don't allow startups or home businesses to develop for their hardware at all. This leaves Xbox Live Indie Games, which requires all programs to be in verifiably type-safe IL that doesn't use System.Reflection.Emit. That sort of limits one to C# or C++-in-name-only that isn't compatible with standard C++ (e.g. different incompatible syntax for pointers and references). And you usually want to write the game logic once (Don't Repeat Yourself), and this means using the same language for the game logic portion of the Android version that you used for the Xbox 360 version.

    20. Re:The nebulous danger by Anonymous Coward · · Score: 0

      MS have a long history of encouraging people to commit to follow them, and then swerving like mad to [lose] them.

      So what?

      If Microsoft "swerves" and changes the C# standard, will F-spot, Tomboy, GNOME Do, and my other apps stop working suddenly?

      The Linux users of C# don't have to care about the official standard. If Microsoft forks C#, they wouldn't have to try to keep up.

    21. Re:The nebulous danger by Anonymous Coward · · Score: 0

      I'm pretty sure that X has functions that do exactly this, and has for a very long time. Maybe not exactly two arguments, but the idea is there and has been fleshed out enough and for long enough that a court is likely to conclude that passing around events like that is obvious to a person skilled in the art, thus invalidating the patent.

      I am not a lawyer, and I am not acting as a lawyer. The above is for entertainment purposes only. Consult with your lawyer before using any of the above opinion. Consult with your physician before reading.

    22. Re:The nebulous danger by makomk · · Score: 1

      I'm pretty sure that X has functions that do exactly this, and has for a very long time. Maybe not exactly two arguments, but the idea is there and has been fleshed out enough and for long enough that a court is likely to conclude that passing around events like that is obvious to a person skilled in the art, thus invalidating the patent.

      Which is why Microsoft didn't just patent passing around events like that: instead they patented passing around events like that using .Net delegates, which in the eyes of the patent office makes it different enough to be eligible for patent protection. That's what makes Mono so dangerous.

    23. Re:The nebulous danger by jabjoe · · Score: 1

      But Mono aims to be compatible. If they give up that, that would be one less problem I have with them. However, MS haven't really started the swerving to control the standard yet, they are still very much in the growing the standard part of the cycle.

  27. A human-to-smartphone infection? by Arancaytar · · Score: 1

    And here we keep telling clueless users that "it's not that kind of virus."

  28. Cross platform compatibility! by Locke2005 · · Score: 1

    Let's see, Windows Phone apps are written in C#, iPhone apps are written in Objective C, and Android Apps are written in Java... so obviously using Mono on all three is going to be a big win for cross platform programming!

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
    1. Re:Cross platform compatibility! by Anonymous Coward · · Score: 0

      And a huge loss for end users.

    2. Re:Cross platform compatibility! by Billly+Gates · · Score: 1

      I am thinking it might be the newest cool thing to use that all the developers would want to use. It would help stop giving mono a bad name. I mean who wouldn't want to write an app once and run it anywhere! Hmm this sounds familiar?

      Anyway, it is not cheap as another poster pointed out at $1,000 for just the compiler and more for Visual Studio plugins. Most apps never make money so hobbiests such as myself will keep using Eclipse and Google's free SDKs. While Iphone hackers will just pay $100 for Xcode.

      If people did not prefer free maybe there could be a market for these tools but $2,99 at the most would mean you would need to sell hundreds if not thousands of apps just to break even to cover the costs of the tools.

  29. Can we get... by NecroPuppy · · Score: 1

    Penicillin for Android next?

    To help with mono infections?

    (Yes, I know penicillin doesn't work on real world mono. It's a joke.)

    --
    I like you, Stuart. You're not like everyone else, here, at Slashdot.
    1. Re:Can we get... by SplashMyBandit · · Score: 1

      Would have been funnier if you had said, "Acyclovir" (which does have action against the Herpes Simplex virus, aka "Mono") :)

  30. Re:First post! by darthdavid · · Score: 1

    Every time you do that god kills a kitten...

  31. Yeah, but... by Anonymous Coward · · Score: 0

    what we really want to know if what the Expensify CEO think about this. I'll wait to find out what the Oracle of Frisco decrees...

  32. The answer is No. by theBully · · Score: 2

    I am a programmer and I program in C# sometimes. C# like Java, VB, etc. was established with the idea of high level quick programming. A programming language that allows anyone to program. The problem with it is, that, anyone programs in it. I won't go to say that you can't program hard core staff with it...just most of its programmers don't.

    Mono, is a framework and not a programming language. And it does incorporate the basic stuff of the .Net framework. Having that said it's not a bad framework and brings the ability to develop cross-platform in C#. However, the fact that it only includes the basics disables that "rapid programming" paradigm which exists around C# + .Net in quite a large part.

    Programming cross-platform has never been and never will be trivial. Java offers that capability at a high performance cost (still). Also, looking at many OSS developments in Java I tend to think that it brews bad habit. Again, that might not be Java, it may be simply poor programmers and poor architects.

    If searching for that "one language to rule them all, one framework to rule them all" grail, have a look at C/C++ and the standard libraries. But don't look at that as being the fastest development path. It's simply the smallest common denominator and that poses some challenges. Programming cross-platform is definitely not an easy task and not for everyone.

    Food for thought: Not all software has to be cross-platform.

    1. Re:The answer is No. by wasabii · · Score: 1

      Actually, Mono runs all of the non-UI and non-WCF 4.0 code I have. Just fine. And it runs most of the WCF client side stuff just fine.

      That includes Linq, and almost everything everybody uses on a daily basis.

      It should be pointed out that Mono doesn't magically make the UI differences between iOS, Android and whatever go away. You still have to use native widgets per platform.

      So, you can make a core assembly, that you share between all three, and independent UI's on top of that. Sounds like a great situation to me.

    2. Re:The answer is No. by krazytekn0 · · Score: 1

      Thank you, I totally agree. I mean, I sit here with a phone with a 1ghz processor that can barely run simple applications at an acceptable speed, because it's java. running CLI programs through the terminal does show that it has the speed in there somewhere.

      --
      Not all life is cyber. Extra Income
    3. Re:The answer is No. by ADRA · · Score: 1

      Win/IOS/Android all support core C libraries as well, so there needs to be compelling reasons to use .NET over C if portability is the top concern.

      --
      Bye!
  33. Re:.NET - where deployment is just a word by Mr2001 · · Score: 3, Funny

    I can write a .NET program on native windows and when I launch the EXE on a machine with no .NET it will simply fail with an error number. It doesn't ask you if you want to put .NET on or even explain to you that you need it to run the program, it just fails.

    So... the same thing that happens whenever you launch any other program with its required libraries missing? Try copying a native VC++ program to a system that doesn't have the VC++ runtime installed. It won't spoon-feed you information about what the VC++ runtime is, why you need it, where to get it, and how to install it; it'll just give you a cryptic error.

    If you want to do deployment properly, you need an installer. With Visual Studio it's dead simple to make a setup program that'll check for prerequisites like .NET and install them automatically.

    --
    Visual IRC: Fast. Powerful. Free.
  34. OpenStep! by Anonymous Coward · · Score: 0

    .NET is to mono as Cocoa is to GNUStep. Compatible in theory, unused in practice.

  35. I rather use QT by Anonymous Coward · · Score: 0

    Plus it also use NDK I don't know how to program in java, and I refuse to learn java.
    http://labs.qt.nokia.com/2011/02/28/necessitas/

  36. oh well by Anonymous Coward · · Score: 0

    i have to inspect the program before i download it so that i don't get patenttrap mono on my android phone

  37. if(comment.Premise.HasValue) by Anonymous Coward · · Score: 1

    Use the HasValue property to check for null without causing an exception. Doesn't make that much sense to me, but it's not hard either.

    C# and Linq To SQL is still way better than Java. I wonder if all this functionality will make it into Android...

  38. mono came shortly after the taste app by Life2Death · · Score: 0

    This also is during the arrival of smell and taste addition to the iPad, as seen on TV news

  39. Oh please please please please by pookemon · · Score: 1

    Dear Microsoft,

    If you were smart, you'd reinstate your Java to C# converter.

    Signed,

    Fed up Java dev...

    --
    dnuof eruc rof aixelsid
  40. Hrm, I thought it was a bit sluggish recently. by Anonymous Coward · · Score: 0

    End of Line

  41. Re:First post! by bertoelcon · · Score: 1

    But it's not fixing the stray cat problem around my house.

    --
    Anything can be found funny, from a certain point of view.
  42. Kill it with fire by bl8n8r · · Score: 1

    anything novell is offering is better suited for use as an example of what *not* to use. sorry, but someone please kill mono with fire, and while your at it, drive a wooden stake through the lump under the blanket next to it - silverlight.

    --
    boycott slashdot February 10th - 17th check out: altSlashdot.org
  43. Not correct by SuperKendall · · Score: 1

    Mono is not a language

    Although you are technically correct that Mono is not a language, Mono IS a mechanism to use the C# language.

    From there to actually develop applications for the iPhone, you make use of the Apple frameworks, which Mono has handily wrapped in C# wrappers.

    So I wouldn't say it's "less" than anything, it's just basically a way to use C# for different platforms while still using the native libraries they offer.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Not correct by greap · · Score: 1

      Although you are technically correct that Mono is not a language, Mono IS a mechanism to use the C# language.

      From there to actually develop applications for the iPhone, you make use of the Apple frameworks, which Mono has handily wrapped in C# wrappers.

      No, Mono is a mechanism to use the CLR. I can quite hapily use any language I have an IL compiler for, there are some available under the mono platform for c# and vb.net etc, or I can use my MS ones under windows and run my assemblies under mono on nix.

  44. Dance with the devil by symbolset · · Score: 1

    Dance with the devil and you will pay his fee. There is no point to this. This Microsoft crap adds nothing you can't get without the taint.

    --
    Help stamp out iliturcy.
  45. Mono may never catch up by Anonymous Coward · · Score: 0

    The real problem is that Mono only supports .NET 2.0.

    The significant benefits available in newer released unfortunately tie .NET more and more to the Windows platform, though Mono could still incorporate a lot more than it does currently.

    As a c# 4.0 Dev, but a long standing Linux advocate, I unfortunately cannot develop for Mono because it is so out dated and I have become very accustomed to utilizing all the contemporary language features such as lambdas, linq, expression trees, anonymous types, etc.

    Visual Studio 2010 also provides a development experience which Mono developers can only dream of (though it is not without its problems, as with any M$ product of course)

    1. Re:Mono may never catch up by Tacvek · · Score: 1

      Mono has support for the language C# 4.0 targeting the CLI. The libraries may not be fully caught up with the libraries that ship with .NET 4.0, but the most important pieces are there. I'm not sure why you think otherwise.

      Even Mono for Android is advertised as supporting a subset of .NET 3.5 (which uses C# 3.0) which includes all the languages features you mentioned.

      Mono for Android even uses a Visual Studio plugin, making Visual Studio its preferred development environment.

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    2. Re:Mono may never catch up by wasabii · · Score: 1

      Actually Mono runs 4.0 code just fine. Obviously you can't use WPF on it.

  46. I wouldn't touch it by Anonymous Coward · · Score: 0

    Mono: don't you get it! Mono is something to avoid (literally) like the plague! Its got crappy mickeysoft technology (which is bad enough), but its tied in mickeysoft legalese. The GPL is good. Mickeysoft legalese is bad. They no doubt have submarine patents all over this junk. With all the bright lights over at Google, none of them clue up about the legal minefields around this. So here's the first, last and only clue from me to the mavens over at Google: Stay Away From This! Mono: Don't You Catch It! Was that so hard?

  47. PYTHON!!! by knapper_tech · · Score: 1

    Death to curly braces and semicolons. We should just erase them from ASCII already. Disaster. Absolute worst way to organize language ever.

    What does Java have that Python doesn't in two weeks?

    --
    "There are some people that if they don't know, you can't tell them." ~ Louis Armstrong
    1. Re:PYTHON!!! by ADRA · · Score: 1

      Seriously? Python's dependence on strict and unwavering structural significance to character placement just harkens me back to COBOL which I'd inflict on nobody. The love you have for implicit statement and loop characteristics is the single reason why you'll never see python spread beyond niche crowds.

      --
      Bye!
  48. .Net is not a programming language. by Anonymous Coward · · Score: 0

    .Net is not a programming language.

    Common misconception.

    It is a huge pile of junk m$ cobbled together to try and play catchup with everyone else and consolidate the glorious mess that was DCOM.

    I don't even agree with Mono, I think its a waste of time, but then I use Wine and more and more m$ apps are written on this garbage platform.

    Roll on full hardware virtualization I say.

    1. Re:.Net is not a programming language. by dolmen.fr · · Score: 1

      It was also the major Microsoft strategy to move developers from a 32 bits environment. .NET makes applications less dependent on the underlying OS architecture, and that was a good move for them to have developers to make applications working on 64 bits Windows.

  49. Re:First post! by FatdogHaiku · · Score: 1

    Every time you do that god kills a kitten...

    and uses the fur to wrap a pair of handcuffs so you can get off the way you should, via punishment!

    --
    You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
  50. It's always a trap with these guys. by symbolset · · Score: 2

    It this succeeds, it validates their development framework: "See, it's so good the freetards even abandon their precious GNU and Java for it." But Miguel cannot possibly keep mono current, so the thing will always be obsolete. And then whenever MS wants they can shut down not only Mono, but all the projects built with it. That's the crippling blow they are waiting for. They are already directly suing over Android and that's not even slightly derived from MS products.

    There are just too many good toolchains to invest the grey matter and training time in this trap.

    --
    Help stamp out iliturcy.
    1. Re:It's always a trap with these guys. by hairyfeet · · Score: 0

      Dude its been eleven years already and NOTHING...zip nada squat zilcho...I think by this point it is safe to call FUD in the case of the FOSS advocates because any attempt by MSFT now would most likely get their asses kicked in court under latches.

      So give it a rest already. What are you gonna say in the 7 or 8 years when the patents will have run out? "Oh but they may have figured out how to hide the longest submarine patent in history"? Bullshit is bullshit no matter WHO slings it and by claiming "its a trap!" this late in the game (although I will give you credit for not writing M$, but I bet you were tempted, weren't you?) it simply makes FOSS look like a bunch of tinfoil hatters. IS that REALLY how you want FOSS to be seen?

      How about instead of FUD you simply tell developers to try the different languages and choose the best tool for the job they have. FOSS is all about choice, yes? or is it only about choices you agree with? But if the best argument you have against C# is magical hidden patents that have NEVER been seen or used? Well then you really have no argument at all.

      Oh and this master plan to "kill Linux"? Get over yourself, you aren't that big a target anymore. The new hotness is iOS, which is why MSFT is sinking billions into acquiring Nokia. Google has pretty much locked Linux out of the game (How's that 3.0 source code?) by refusing to allow GPL V3 so that it can TiVo trick the code away from the users and developers, RIM is dead, that leaves HP, MSFT, and the big boy Apple. The HP option will probably again be TiVo tricked, so the only real targets are Google and Apple. Linux? I doubt its even on the radar anymore.

      But if you really think MSFT is gonna sink hundreds of millions into a successor to VB, all in this insanely loooooong winded plot to kill Linux? You might want to check your tinfoil hat, it is probably on too tight. If MSFT wanted Linux dead buying the top 20 developers would cripple it in a heartbeat and leave it waaaaay behind. Hell Oracle is a bigger threat to Linux now than MSFT, you just aren't a big enough fish in the new market to be a target, sorry.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    2. Re:It's always a trap with these guys. by oh_my_080980980 · · Score: 2

      Ummm SCO. And recently Microsoft has launched a lawsuit against Google over Android in regards to patent infringement.

      Read much.

    3. Re:It's always a trap with these guys. by Compaqt · · Score: 1

      I don't see how Android isn't Linux.

      Anyway's MS has already launched a patent war on Android.

      The only reason it doesn't do the same for Linux desktops and technologies used there (including Mono) is it doesn't see it as a threat. The doctrine of laches didn't prevent MS from suing over Linux tech which has presumably been in the kernel for a while.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    4. Re:It's always a trap with these guys. by hairyfeet · · Score: 0

      Yep in 30 damned years they've launched a grand total of SEVEN, count them seven, patent/copyright lawsuits. And MSFT has historically offered RAND, as in reasonable and non discriminatory, licensing on their patents and copyrights for ages. Notice how NOBODY during the TomTom suit pointed out MSFT had offered them RAND on Fat32 and got the finger in return? How many suits and motions does the FSF file yearly? I bet its more than seven. If MSFT wanted to drop the patent bomb they would have done so back in the WinME days.

      And yes latches would cover technology they expressly handed to the public through their agreement not to sue. Any court would laugh the thing out before it even got to pre-trial. And SCO? Again you are talking ancient history, hell Gates was still running the company when that thing started. Its old news.

      What you SHOULD be watching, and what I'm gonna ROFLMAO when it bites you right in the ass, is Google. Google is getting ready to skullfuck the whole community but the fanbois are too busy kissing their ass to see it coming. Google has been VERY careful to avoid ANY and all GPL V3, why is that? I'll tell you why it is because GPL V2 might as well be PD and both Google and any other corp KNOWS this. The developers that wrote all those neat embedded programs are gonna get nothing for their trouble but the finger and code they can't run thanks to code signing and eFuses.

      So please, keep sling the FUD and planning yesterday's war, while leaning up against the big bad wolf in sheep's clothing. Google has kept ALL of the decent stuff internal, simply so they won't have to share, and now with 3.0 they are starting to lock things up. Thanks to TiVo GPL V2 will be the new BSD, with any and all corps filling their boots while giving you...hell anything they want, it isn't like you'll be able to run the code to see if it works or not anyway. Meanwhile I'll LMAO at the naivete of the community who thought because Google used some of their code that they were friends. the ONLY friend Google has IS GOOGLE, period. You are about to be train banged and don't even see it coming, because you're too busy writing M$ and thinking like it is 1997. WAKE UP!

      --
      ACs don't waste your time replying, your posts are never seen by me.
  51. What bad blood? by dolmen.fr · · Score: 1

    will the bad blood between the F/OSS groups and Microsoft make this a dead end?

    What "bad blood"? There was a Mono presentation by Novell at the Microsoft TechDays 2011 in february in Paris. I was there.

    Can't find an official page on the official site. But here is a link in french. http://blogs.dotnet-france.com/jeanphilippeg/post/TechDays2011-Mono-et-son-ecosysteme.aspx

  52. We have python already by Billly+Gates · · Score: 1

    Google released C and C++ tools as well.

    It would be cool if Android includes Java 7 lambda so more languages could be ported. Python is not officially supported but is a hack of Jython as it runs unmodified on android. Any app would have to include it to run.

  53. Yeah, but... by jonaskoelker · · Score: 1

    Is the ring red?

  54. No way! by miffo.swe · · Score: 1

    I wont let mono anywhere near my phones and will strongly advice against it to anyone i know.

    Mono is a big red flag with Microsoft infront of it just waiting to attack. Microsoft is in an all out patent war against anything related to Android and Linux.

    --
    HTTP/1.1 400
  55. Lie down with dogs by ThatsNotPudding · · Score: 1

    get up with blood-sucking, litigious fleas.

  56. Oh you mean like by benjymouse · · Score: 1

    someNullableInt ?? 0

    --
    Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
  57. anyone have some experience with this yet by hesaigo999ca · · Score: 1

    Anyone have some secrets they might want to share about this ...I was thinking about getting into it, dont know if it is properly established yet as a framework...

  58. EAFP by tepples · · Score: 1

    Who comes up with data structures that throw an exception because you asked it if something was inside and the answer was 'no'?

    Guido, that's who. One of the Pythonic principles is that forgiveness (try/except) is easier than permission (testing first).

    1. Re:EAFP by Just+Some+Guy · · Score: 1

      Guido, that's who. One of the Pythonic principles is that forgiveness (try/except) is easier than permission (testing first).

      You beat me to it. What's the appropriate sentinel value to return from an unsuccessful data structure query? 0? Not helpful if you're storing integers. False? Doesn't help if you have some boolean values. Empty string? There are lots of valid reasons to store empty strings in a hash table. "None"? Same as strings.

      The Python (and .NET, if you believe the OP) approach of throwing exceptions makes a lot more sense than something like "if(value = get('foo') == 0) { printf("not found\n");}" for most situations.

      --
      Dewey, what part of this looks like authorities should be involved?
  59. .NET-only platforms by tepples · · Score: 1

    To me it looks as if it would be counter-intuitive and suicidal to start going after everyone over Mono. It would kill the language everywhere, including Windows.

    Would it kill the .NET languages on Xbox Live Indie Games and Windows Phone 7, which can't use anything but .NET languages?

  60. Exceptions in generator expressions by tepples · · Score: 1

    What's the appropriate sentinel value to return from an unsuccessful data structure query?

    Null pointer. In Python, some_dict.get('tires') returns None if tires don exits in the dictionary. Likewise, in PHP, @$some_array['tires'] returns null (the @ means turn warnings into null returns). For extra credit, the caller could specify the sentinel value, which Python incidentally allows as the second optional argument to dict.get(key, sentinel=None).

    The Python (and .NET, if you believe the OP) approach of throwing exceptions makes a lot more sense than something like "if(value = get('foo') == 0) { printf("not found\n");}" for most situations.

    Unless you're trying to write something in a functional paradigm, such as in a Python generator expression. There is no facility for try/except within Python generator expressions; instead, you have to def an inner function and catch the exception inside that. (But then the details of Python are probably off-topic here, as the cases where you'd need Mono probably involve portability to some platform without the System.Reflection.Emit that IronPython requires.)

    1. Re:Exceptions in generator expressions by Just+Some+Guy · · Score: 1

      To clarify, I was asking an illustrative question to point out that there's no "perfect" sentinel value for all circumstances, and I prefer Python's raise-on-failure paradigm. I don't know whether OP was correct about .NET working that way, it's not an inherently crazy design decision.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Exceptions in generator expressions by exomondo · · Score: 1

      To clarify, I was asking an illustrative question to point out that there's no "perfect" sentinel value for all circumstances, and I prefer Python's raise-on-failure paradigm. I don't know whether OP was correct about .NET working that way, it's not an inherently crazy design decision.

      He is correct wrt nullable types, however nullable types only raise that exception if you've tried to use an undefined value without putting a guard checking the result of 'HasValue' first.

  61. Eh.. not available for Linux... ? by karimlalani · · Score: 1

    Did I miss something or is this Mono for Android not going to be available on Linux?

  62. The game logic need not change by tepples · · Score: 1

    Windows Phone 7 is stillborn

    Even after Nokia's deal?

    Porting [Xbox 360 Indie] games to a phone is still going to require a major rewrite anyways

    How so? I've read reports that porting between XNA on WP7 and XNA on Xbox 360 requires 1. rewriting the input and 2. using lower detailed meshes and textures on the phone. That's it. Even in a case where you'd have to replace the entire graphics engine, such as between XNA and Mono for Android, game logic elements such as collision detection and enemy behaviors would remain unchanged across platforms that support the same programming language. See my article about multitier architecture.

    1. Re:The game logic need not change by tomhudson · · Score: 1

      The Nokia deal has the "smell of death" around it. Nokia said they won't be introducing any WP7 smartphones until 2012, which is an eternity in today's market. They're going to miss the back-to-school crowd, the Black Friday crowd, and the biggie - the Christmas holiday season. (see the last 8 paragraphs).

      No wonder Microsoft had to kick in a billion dollars .... there's no other way that the deal could even begin to make any sort of sanity.

      Now as for the game porting, some games are very dependent on screen size. Bejeweled is something you wouldn't waste your time with on a big-screen TV, and SimCity or Flight Simulator isn't something that lends itself to being anything more than an exercise in eyestrain on a cell phone.

      Sure there are games that will still work, no matter what the resolution, but the smaller the display, the less perceived value in a game, so while the work is about the same, the income is a lot less, so unless you can get the phone version out as a low-cost side-line to the main event ....

      I'm not saying it's something people shouldn't consider, just that there are several factors against it:

      1. lower revenue per sale compared to all other channels;
      2. time spent porting could be used to create original content better suited to the form factor instead of "Shovel-Ware 2.0";
      3. mono is always going to be behind compared to the microsoft product ...
      4. your collision detection and enemy behaviors logic would remain pretty much unchanged on Android/Java/Dalvik as well.
    2. Re:The game logic need not change by tepples · · Score: 1

      Now as for the game porting, some games are very dependent on screen size.

      And others are not. Something like Super Mario 64 is much the same experience on N64 or DS, modulo input changes. Something like New Super Mario Bros. is much the same experience on DS or Wii.

      Bejeweled is something you wouldn't waste your time with on a big-screen TV

      Yet Tetris sells on both the consoles and the handhelds.

      SimCity or Flight Simulator isn't something that lends itself to being anything more than an exercise in eyestrain on a cell phone.

      Xbox 360 games also have to support SDTVs. Anything that's eyestrain on an SDTV is also eyestrain on a phone, and vice versa. Capcom ignored this at its own peril.

      the smaller the display, the less perceived value in a game

      In that case, thank $deity for larger tablets like Archos 101 and Motorola XOOM.

      so while the work is about the same, the income is a lot less, so unless you can get the phone version out as a low-cost side-line to the main event

      And that's how support for C# on Android makes Xbox 360 to Android ports "a low-cost side-line", involving only changes to the graphics engine, rather than an expensive line-by-line rewrite of the core game logic.

      your collision detection and enemy behaviors logic would remain pretty much unchanged on Android/Java/Dalvik as well.

      The logic would be the same, but without support for C# on Android or support for Java on Xbox 360, the code would have to be translated by hand between C# and Java. Corrections to one would not automatically be reflected in the other. The last thing you want is for the player to be able to make a jump on one platform and not be able to make the same jump on another because the physics differ.

  63. HairyFeet's "GREATEST HITS", PART DEUX ("NOT!") by Anonymous Coward · · Score: 0

    See subject-line above, & these "prime examples" below via links to the originals of WHY hairyfeet shouldn't have gone to "ITT Tech", in his TECHNICAL BLUNDERS, & more (regarding HOSTS files):

    ---

    Static vs. Dynamic Adbanner addressing (lol, "according to hairyfeet"):

    (Which even BestBuy Techs know!)

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35681060

    ---

    DNS Client Cache turn off for HOSTS, a TECHNICAL Blunder by Hairyfeet:

    (Which even BestBuy Techs know also (just like the one above!))

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35686054

    ---

    Hairyfeet's single solutions SECURITY FAILURES? See inside:

    http://slashdot.org/comments.pl?sid=2064694&cid=35690260

    ---

    Your sources on "security" vs. mine (actual security people) (AND myself, a source on it):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690328

    ---

    Lastly, as to your LIBEL of myself (w/ arstech):

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35668740

    ---

    The defeat of hairyfeet by APK (video analogy - hilarious, BUT, apt):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690536

    ---

    They say it all, & usually vs. hairyfeet's own words quoted! I wouldn't pay him too much heed, especially after you read the above b.s., lies, changing figures, & even LIBEL of others that hairyfeet likes to do. After all - he's from "ITT Tech" (student)...

    Worst part of ALL, here?

    Hairyfeet just clearly doesn't even understand how HOSTS files benefit you for:

    ---

    1.) ADDED Reliability (vs. DNS going down, or being 'poisoned', & even DNSBL (DNS Block Lists))

    2.) ADDED "layered" Security online (vs. known bad sites &/or servers (botnet C&C) + maliciously scripted adbannners by BLOCKING them out)

    3.) ADDED Speed (not loading adbanners, and hardcoding your fav. sites into it)

    4.) Even more ADDED 'anonymity' online (vs. DNS request logs)

    (Even server admins might NOT mind having the load on their DNS servers lightened up also, bonus!)

    ---

    APK

    P.S.=> Personally though - because hairyfeet is only a "techie"? I suspect he doesn't want people to know about HOSTS files' added LAYERED SECURITY benefits to the end-user: Why?? Because if users stop getting so much "malware-in-general" which layered security (and HOSTS) give you added layered protection against, he's out money...apk

  64. HairyFeet's "GREATEST HITS", PART DEUX ("NOT!") by Anonymous Coward · · Score: 0

    See subject-line above, & these "prime examples" below via links to the originals of WHY hairyfeet shouldn't have gone to "ITT Tech", in his TECHNICAL BLUNDERS, & more (regarding HOSTS files):

    ---

    Static vs. Dynamic Adbanner addressing (lol, "according to hairyfeet"):

    (Which even BestBuy Techs know!)

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35681060

    ---

    DNS Client Cache turn off for HOSTS, a TECHNICAL Blunder by Hairyfeet:

    (Which even BestBuy Techs know also (just like the one above!))

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35686054

    ---

    Hairyfeet's single solutions SECURITY FAILURES? See inside:

    http://slashdot.org/comments.pl?sid=2064694&cid=35690260

    ---

    Your sources on "security" vs. mine (actual security people) (AND myself, a source on it):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690328

    ---

    Lastly, as to your LIBEL of myself (w/ arstech):

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35668740

    ---

    The defeat of hairyfeet by APK (video analogy - hilarious, BUT, apt):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690536

    ---

    They say it all, & usually vs. hairyfeet's own words quoted! I wouldn't pay him too much heed, especially after you read the above b.s., lies, changing figures, & even LIBEL of others that hairyfeet likes to do. After all - he's from "ITT Tech" (student)...

    Worst part of ALL, here?

    Hairyfeet just clearly doesn't even understand how HOSTS files benefit you for:

    ---

    1.) ADDED Reliability (vs. DNS going down, or being 'poisoned', & even DNSBL (DNS Block Lists))

    2.) ADDED "layered" Security online (vs. known bad sites &/or servers (botnet C&C) + maliciously scripted adbannners by BLOCKING them out)

    3.) ADDED Speed (not loading adbanners, and hardcoding your fav. sites into it)

    4.) Even more ADDED 'anonymity' online (vs. DNS request logs)

    (Even server admins might NOT mind having the load on their DNS servers lightened up also, bonus!)

    ---

    APK

    P.S.=> Personally though - because hairyfeet is only a "techie"? I suspect he doesn't want people to know about HOSTS files' added LAYERED SECURITY benefits to the end-user: Why?? Because if users stop getting so much "malware-in-general" which layered security (and HOSTS) give you added layered protection against, he's out money...apk

  65. WTF? by symbolset · · Score: 1

    Microsoft? The key to Android app portability? What the heck are you smoking?

    --
    Help stamp out iliturcy.
    1. Re:WTF? by tepples · · Score: 1

      If you want your program to be portable between Android phones and a set-top video game player, you have to deal with Microsoft.

      Microsoft? The key to Android app portability? What the heck are you smoking?

      It's not that Microsoft is the key to portability as much as that Nintendo and Sony have made the choice to allow Microsoft to be the only relevant outlet for smaller set-top game development efforts.

  66. Re:words of wisdom, from Baraq Hussein Obama: by spun · · Score: 0

    We won, you lost, despite your side outspending ours 4 to 1. And Prosser was a shoe in! He got 99.54% of the vote last time! You can keep on whining and spinning, I will let you keep doing that as it must provide you with some small comfort. In short, be prepared to lose your majority in the house next election, as well as most of the governor's seats you picked up. We won't let you traitors fuck up our country.

    --
    - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
  67. Reply of your Questions by sawanswer · · Score: 1

    Hi .. i read your all questions and if you really want to get the reply and really ask and wants more questions and answer then i am putting the link here for all of you there you may get all better quality answers. And also if you are interested to ask questions then you may ask too. The link is under below! http://www.sawanswers.com/

  68. HairyFeet's "GREATEST HITS", PART DEUX ("NOT!") by Anonymous Coward · · Score: 0

    See subject-line above, & these "prime examples" below via links to the originals of WHY hairyfeet shouldn't have gone to "ITT Tech", in his TECHNICAL BLUNDERS, & more (regarding HOSTS files):

    ---

    Static vs. Dynamic Adbanner addressing (lol, "according to hairyfeet"):

    (Which even BestBuy Techs know!)

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35681060

    ---

    DNS Client Cache turn off for HOSTS, a TECHNICAL Blunder by Hairyfeet:

    (Which even BestBuy Techs know also (just like the one above!))

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35686054

    ---

    Hairyfeet's single solutions SECURITY FAILURES? See inside:

    http://slashdot.org/comments.pl?sid=2064694&cid=35690260

    ---

    Your sources on "security" vs. mine (actual security people) (AND myself, a source on it):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690328

    ---

    Lastly, as to your LIBEL of myself (w/ arstech):

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35668740

    ---

    The defeat of hairyfeet by APK (video analogy - hilarious, BUT, apt):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690536

    ---

    They say it all, & usually vs. hairyfeet's own words quoted! I wouldn't pay him too much heed, especially after you read the above b.s., lies, changing figures, & even LIBEL of others that hairyfeet likes to do. After all - he's from "ITT Tech" (student)...

    Worst part of ALL, here?

    Hairyfeet just clearly doesn't even understand how HOSTS files benefit you for:

    ---

    1.) ADDED Reliability (vs. DNS going down, or being 'poisoned', & even DNSBL (DNS Block Lists))

    2.) ADDED "layered" Security online (vs. known bad sites &/or servers (botnet C&C) + maliciously scripted adbannners by BLOCKING them out)

    3.) ADDED Speed (not loading adbanners, and hardcoding your fav. sites into it)

    4.) Even more ADDED 'anonymity' online (vs. DNS request logs)

    (Even server admins might NOT mind having the load on their DNS servers lightened up also, bonus!)

    ---

    APK

    P.S.=> Personally though - because hairyfeet is only a "techie"? I suspect he doesn't want people to know about HOSTS files' added LAYERED SECURITY benefits to the end-user: Why?? Because if users stop getting so much "malware-in-general" which layered security (and HOSTS) give you added layered protection against, he's out money...apk

  69. "Pwufessuh HaiwyPheet's GREATEST HITS" (NOT!) by Anonymous Coward · · Score: 0

    See subject-line above, & these "prime examples" below via links to the originals of WHY hairyfeet shouldn't have gone to "ITT Tech", in his TECHNICAL BLUNDERS, & more (regarding HOSTS files):

    ---

    Static vs. Dynamic Adbanner addressing (lol, "according to hairyfeet"):

    (Which even BestBuy Techs know!)

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35681060

    ---

    DNS Client Cache turn off for HOSTS, a TECHNICAL Blunder by Hairyfeet:

    (Which even BestBuy Techs know also (just like the one above!))

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35686054

    ---

    Hairyfeet's single solutions SECURITY FAILURES? See inside:

    http://slashdot.org/comments.pl?sid=2064694&cid=35690260

    ---

    Your sources on "security" vs. mine (actual security people) (AND myself, a source on it):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690328

    ---

    Lastly, as to your LIBEL of myself (w/ arstech):

    http://it.slashdot.org/comments.pl?sid=2061048&cid=35668740

    ---

    The defeat of hairyfeet by APK (video analogy - hilarious, BUT, apt):

    http://slashdot.org/comments.pl?sid=2064694&cid=35690536

    ---

    They say it all, & usually vs. hairyfeet's own words quoted! I wouldn't pay him too much heed, especially after you read the above b.s., lies, changing figures, & even LIBEL of others that hairyfeet likes to do. After all - he's from "ITT Tech" (student)...

    Worst part of ALL, here?

    Hairyfeet just clearly doesn't even understand how HOSTS files benefit you for:

    ---

    1.) ADDED Reliability (vs. DNS going down, or being 'poisoned', & even DNSBL (DNS Block Lists))

    2.) ADDED "layered" Security online (vs. known bad sites &/or servers (botnet C&C) + maliciously scripted adbannners by BLOCKING them out)

    3.) ADDED Speed (not loading adbanners, and hardcoding your fav. sites into it)

    4.) Even more ADDED 'anonymity' online (vs. DNS request logs)

    (Even server admins might NOT mind having the load on their DNS servers lightened up also, bonus!)

    ---

    APK

    P.S.=> Personally though - because hairyfeet is only a "techie"? I suspect he doesn't want people to know about HOSTS files' added LAYERED SECURITY benefits to the end-user: Why?? Because if users stop getting so much "malware-in-general" which layered security (and HOSTS) give you added layered protection against, he's out money...apk