Slashdot Mirror


The Mono Mystery That Wasn't

jammag writes "It was shocking news, or so it seemed: Miguel de Icaza, the Mono creator, was switching his opinion about his life's work — he now seemed to agree with the free software partisans who oppose his Mono work and his Microsoft connections. The story flamed across the Internet and even got picked up on Slashdot. But Bruce Byfield reports that 'De Icaza has not changed his opinions.' De Icaza calls the rumors 'a storm in a teacup.' Tracing the misinformation trail, Byfield concludes that 'the FOSS community excels at communication. However, in this instance, that ability was used irresponsibly.'"

51 of 268 comments (clear)

  1. Inflamatory headling superceeds mundane content? by RingDev · · Score: 4, Funny

    Inflammatory headline supersedes mundane content? Say it ain't so!

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
  2. Lets get more rumors started. by gad_zuki! · · Score: 4, Funny

    Didnt you hear? Stallman converted to scientology and Linus is accepting patches from NAMBLA!! Oh and the EFF finally released its spec for its homegrown DRM scheme.

    1. Re:Lets get more rumors started. by santax · · Score: 3, Funny

      Why drag the North American Marlin Brando Look ALikes into this?

    2. Re:Lets get more rumors started. by squiggleslash · · Score: 3, Funny

      Yeah, and, and, Hans Reiser murdered a woman and then lied to cover it up!

      Oh, that one's real. Sorry about that.

      Mod -1,000,000 "Frankly Totally Tasteless"

      --
      You are not alone. This is not normal. None of this is normal.
  3. I accidentally an entire word by Aurisor · · Score: 2, Informative

    Sorry, that should read:

    We weren't excited by some faux controversy that some no-name newspaper had deleted his article. Speaking for myself and the friends I talked with, we were just mocking De Icaza for being five years behind the entire rest of the world in realizing that dragging a patent-encumbered CLR into Linux just to get some sticky notes on his desktop was a bad idea.

    That's a little bit of hyperbole, but the point remains: this guy has been smoking the good stuff.

    Yes, yes, preview first, etc etc.

  4. Re:Good News by c0d3g33k · · Score: 4, Insightful

    Good news everyone. Icaza is still a whore.

    If you make your living exchanging your talents for money, so are you. So what is your point?

    Stop being so inflammatory. If you have a logical argument to make, make it and we will decide whether the argument is valid based on its merit. Otherwise you just blend into the rest of the noise of modern 'rhetoric' (with apologies to true rhetoric).

  5. Still good for Slashdot... by DMiax · · Score: 4, Insightful

    I can see the editor thinking "we already know this is fake news, but let's publish: we are missing a good Mono flamewar since forever!"

  6. Too bad. I was willing to think he'd grown up. by Just+Some+Guy · · Score: 3, Insightful

    That's a shame. I'd thought that after all this time he was finally wising up and accepting what everyone else on the planet was saying. I guess either he hasn't put his fanatical devotion to his employer aside (does anyone really believe that he didn't get the job he applied for at Microsoft?) or that his boss told him to back down. Either way, too bad. He's a talented guy and I wish he would work on something useful and less poisonous.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:Too bad. I was willing to think he'd grown up. by Abcd1234 · · Score: 4, Insightful

      I'd thought that after all this time he was finally wising up and accepting what everyone else you agree with was saying.

      There, fixed that for ya.

      I know, amazing! Some people might *actually* disagree with you, oh wise and omniscient one!

    2. Re:Too bad. I was willing to think he'd grown up. by psbrogna · · Score: 2, Insightful

      Unfortunately it's not reasonable to expect all of the people who use IT to be able to logically evaluate a strategic choice from among the myriad IT paths available. So many follow the crowd betting that by doing so they'll minimize their chance of making a strategic error. I don't think this is to their discredit, strategic decisions are costly to make if you have to plod through all the variables on your own even when you have the expertise to apply logic.

      The phenomenon can lead to an ugly place when deep pocketed (or near-monopolistic) vendors capture enough market share to get the masses on a bad path and ensuing generations of decision makers continue to follow. It is extremely difficult to make a course correction if nobody notices for 20 years- the cost of switching tracks is often prohibitive.

  7. Re:Inflamatory headling superceeds mundane content by miguel · · Score: 5, Informative

    We have announced that our upcoming Mono release (2.8) will default to 4.0:

    http://www.mono-project.com/Roadmap

    For the first time in Mono's history our C# compiler and its supporting engine and core libraries were done before Microsoft released the product, we were usually one to two years behind. This time we are some five months ahead of time:

    http://tirania.org/blog/archive/2009/Dec-09.html

    There are still a handful of loose ends here and there, but luckily, nothing major.

  8. Re:-1 Misses the point by IamTheRealMike · · Score: 3, Insightful

    From Miguels blog

    It took Microsoft eight years, a new management and a fresh set of eyes to change some of these mistakes. The veil of threats that existed over the runtime in 2001 was lifted with the Community Promise announcement but it took eight years, and those were eight years of lost opportunity and FUD directed at all things Microsoft.

    So in fact Miguel was lamenting time lost under a previous, less enlightened management. Not current problems with .NET.

    I remember when Mono was first announced. Miguel at the time argued that the free software world had failed to produce any real competitor to Java or .NET style frameworks despite their absolute dominance of mainstream programming. He didn't think one would appear any time soon either. And guess what - he was right. There is no home grown Linux, Apache or Android equivalent to compete with Java or .NET. And whilst Java is now fully open source, it wasn't safe to assume that'd happen back all those years ago.

    So in fact it seems Miguel was right all along - right about the need, right about the solution, right that Microsoft would not attempt to "destroy Linux" by leveraging patents. Instead they specifically promised in writing not to do that. Why? Probably because they don't care about Linux anymore. The world has moved on, what once seemed like a threat to their business no longer is.

  9. Re:Not that big of a deal by Anonymous Coward · · Score: 3, Insightful

    Wow, grow up, guys. So he has Microsoft connections? So what? If open source affiliation is a valid reason to hate somebody, you might start rethinking your life priorities.

    I don't think it's his "open source affiliations" anyone is worried about, so much as his affiliation with a dangerous monopolist that has been incredibly damaging to the industry and state of the art.

    The Mono project gives Linux developers more choice, especially if they have been working with .NET tech for a long time.

    Yeah, sort of the same way crack dealers give kids more choice of entertainment.

    Would you forfeit years of .NET training and experience because you want to use a Linux platform?

    If I wanted to develop for Linux, I'd absolutely learn new frameworks and tools to do it, but then most people already know multiple languages, tools, and methods of programming.

    at, or I am missing a bigger picture, in such case maybe someone can elaborate in the implications of said "teacup storm"?

    Look up the phrase, "embrace, extend, extinguish". It was MS's strategy and business model to make the Web nonstandard and prevent it from being a viable method of allowing developers and users more choice and functionality instead of being locked into Windows as the only viable way to deliver applications to the majority of users. Now, more than a decade later, if we want to reach the majority of Web users, we're still stuck using most of the same versions of standards as we had then, when MS decided to break the market. .NET is just the same thing over again.

  10. Re:Long story short by The+End+Of+Days · · Score: 5, Insightful

    Miguel doesn't care, because that "99% of us" turns out to be less than 1% of the real "us."

  11. His life's work? by Punto · · Score: 2, Interesting

    Didn't this guy start Gnome (or maybe KDE)? that is actually "life's work" worthy, not something nobody cares about like mono.

    --

    --
    Stay tuned for some shock and awe coming right up after this messages!

  12. Re:Good News by TheCarp · · Score: 4, Insightful

    I never understood whats so immoral or degrading about being a whore. Certainly there are segments of the "sex worker" community that are unsavory and engage in despicable activity (sexual slavery, mental/physical abuse, unfair exploitation) however, there are also those who work freelance and or enjoy their jobs.

    I don't mean to ruin whores for you, I mean, maybe you need to see it as degrading and immoral to get off, your kink is ok I guess. Though, I no more understand that kink than asphyxiation, so it does seem a bit strange to me.

    --
    "I opened my eyes, and everything went dark again"
  13. Re:Not that big of a deal by MightyMartian · · Score: 2, Insightful

    If they're injecting patent bombs into FOSS, then I care, regardless of their intentions.

    Besides, it only goes to show the frailty of modern development education. People get hooked on to languages, and not on to versatility. If a platform doesn't support your favorite development tools, then you either avoid the platform or you adapt and use what there is. It's not like Linux doesn't have a ton of languages. I could understand it if your faced with a choice between assembler and K&R C on one side, and .NET on the other, but there's significantly more choice.

    Don't buy into the Microsoft lockin crap. Even if Mono never turns into the timebomb some of us think it is, the way to become a really good programmer is to work in different development platforms.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  14. Re:-1 Misses the point by Andy+Dodd · · Score: 4, Informative

    "Miguel at the time argued that the free software world had failed to produce any real competitor to Java or .NET style frameworks despite their absolute dominance of mainstream programming."

    Why would they need to? While initially some of the Java trademark and licensing mechanism were semi-unfriendly to open source, the situation was a LOT better than it has ever been with .NET, and is much better now.

    Instead of trying to create a competitor, the OSS community worked with Java - A lot of Java's success can likely be attributed to the participation of the OSS community. (Heck, even Miguel's blog article effectively says this with his citations of various OSS "research" projects into JIT that became mainstream.)

    --
    retrorocket.o not found, launch anyway?
  15. Who cares about core libraries? by Cyberax · · Score: 2, Insightful

    How about WPF, then? When are you going to develop it? I know: never. The scope of it is way too large for your team.

    Same about complete WCF, WWF (and other WTFs).

    So in reality, a Mono application will probably work on Windows, but almost none of Windows C# applications will work on Mono.

    1. Re:Who cares about core libraries? by BassMan449 · · Score: 2, Interesting

      They aren't implementing WPF for the same reason that Microsoft is not adding anything to WPF. MS considers it a dead technology and is pushing SilverLight. Mono is much better off putting the resources into Moonlight than it is into a Mono implementation of WPF.

    2. Re:Who cares about core libraries? by neveragain4181 · · Score: 2, Informative

      I don't think WPF is really that alive, although I agree calling it 'dead' is a bit dramatic.

      Microsoft, as is there frequent pattern, has moved on from WPF in that it's stable but won't be invested in significantly anymore.

      Example: If you take a look at the last major Microsoft conference (MIX10) then you'll see there we no new WPF features added, while a whole bunch of new Silverlight things announced. Even Microsoft realizes that the web is having an impact on their desktop UI strategy, i.e. Silverlight is way good enough and far too similar to WPF to keep two forks alive.

      Saying Silverlight is a 'subset' of a WPF is true, but misses out the portability side, i.e it has it's own run-time. It would be just as true to say that WPF is missing features that Silverlight has.

      WPF isn't dead, it's just resting. (insert parrot joke here-> )

      PS Apologies if you've bet on WPF, you should really have recognized the pattern by now...

    3. Re:Who cares about core libraries? by D4MO · · Score: 4, Informative

      Visual Studio 2010, a core flagship MS product, is written in WPF.

      --

      Rocket science is easy. Neurosurgery, now *that's* difficult.
    4. Re:Who cares about core libraries? by shutdown+-p+now · · Score: 2, Insightful

      Example: If you take a look at the last major Microsoft conference (MIX10) then you'll see there we no new WPF features added, while a whole bunch of new Silverlight things announced.

      That's because the new things in .NET 4 (which includes WPF 4) were announced a long time ago on PDC. There's no point in hashing them over again on MIX in March, when the final version is going to come out in April, and there has been two public betas and RC already, the latter being feature-complete.

      Here is the high-level changelog for WPF 4. As you can see, it contains totally minor and irrelevant features typical of a product being deprecated, such as "the WPF text rendering stack has been completely replaced", or "WPF supports data binding to objects that implement IDynamicMetaObjectProvider" (the latter is a DLR interface that objects written in IronPython, IronRuby, and other similar dynamic language implement to expose their metadata - so it means that you can now bind to Python or Ruby models from WPF views).

    5. Re:Who cares about core libraries? by westyvw · · Score: 3, Funny

      And it shows.

  16. Re:Inflamatory headling superceeds mundane content by mrsteveman1 · · Score: 2, Funny

    What's the difference between Mono and .NET? How does the liberated open source software community connect to these standards? Where does De Icaza fit in the puzzle?

    For this and more, tune in next week for another exciting chapter of "As The Monopoly Turns"

  17. Re:Good News by fejjie · · Score: 5, Interesting

    As someone who actually knows Miguel de Icaza and someone who was there when Mono began, I can tell you with absolute certainty that he started Mono because he truly believes that it's a good platform. As do I and all of the other Mono developers (none of whom get a "fat paycheck" from Microsoft or anyone else). The Mono team is underfunded at Novell, so I and likely other developers have taken a pay CUT in order to work on what we believe in.

    We are not paid to parrot any opinions from Microsoft or Novell. Our opinions are our own and we stand by them.

  18. Re:Inflamatory headling superceeds mundane content by sebt3 · · Score: 2, Informative

    What's the difference between Mono and .NET? How does the liberated open source software community connect to these standards? Where does De Icaza fit in the puzzle?

    Your geek card please... Thanks

    Mono is a free implementation of the .NET infrastructure.

    De Icaza is just the one that started Mono and integrated it into Gnome.

  19. Re:Good News by Ephemeriis · · Score: 2, Insightful

    no, doing degrading and immoral work for money makes one a whore.

    Interesting...

    I assume we're still both talking about whores as in prostitutes - folks who sell sex for money.

    So... What's so immoral or degrading about that?

    Sure, some folks have moral objections to is. And some folks probably find it degrading. But does that mean that prostitution as a whole is automatically immoral and degrading?

    Wouldn't that make something like bartending immoral as well, since some religions have moral objections to alcohol?

    And wouldn't that make pretty much every job on the planet degrading, because I'm sure there's somebody out there who finds it degrading.

    Sure, if you're forced into prostitution against your will... By financial problems, or addiction, or extortion, or whatever... That's bad. But it would also be bad to be forced into anything else against your will.

    And it's certainly true that the political/legal climate here in the US seems to push sex workers into immoral and degrading situations...

    But in areas where sex work is legal, there are plenty of folks who genuinely enjoy their jobs and don't find it immoral or degrading in the least.

    --
    "Work is the curse of the drinking classes." -Oscar Wilde
  20. Re:-1 Misses the point by Dan+Ost · · Score: 2, Interesting

    What does java do that python can't?

    --

    *sigh* back to work...
  21. I know this is Slashdot but... by Timbo · · Score: 5, Insightful

    ...I'm amazed at how obtuse (and in some cases, downright insulting) the majority of the comments on this story are. I think it's highly likely that if .NET didn't come from Microsoft, nobody would be getting quite so emotional about the whole thing.

    For the record, I'm categorically not Microsoft's greatest fan, but you cannot deny that .NET/C# is a damn good platform. Having a portable version of said good platform is therefore a Good Thing. It doesn't matter if Microsoft decide to fuck Mono over; it's still a good platform and therefore still a Good Thing. If you disagree and you don't like it, then fine; don't use it and stop whining.

    1. Re:I know this is Slashdot but... by phantomfive · · Score: 4, Insightful

      I think it's highly likely that if .NET didn't come from Microsoft, nobody would be getting quite so emotional about the whole thing.

      As a matter of fact, that'snot true. The '.net trap' is just another version of the Java trap, only made more dangerous by the fact that Microsoft is known to be hostile to open source.

      If you disagree and you don't like it, then fine; don't use it and stop whining.

      The problem is that mono is included in Gnome, and if it spreads it will get harder and harder to avoid. Some of us would prefer to keep that from happening, because we know what the potential consequences would be.

      --
      Qxe4
  22. Re:-1 Misses the point by binarylarry · · Score: 4, Informative

    Run fast, support multiple languages, provide 99.9999% secure code environments, support more than one thread executing at a time, etc, etc.

    But... Java and Python are two drastically different technologies. Python is great at what it does but it's a scripting language not a virtual platform like Java. .NET is more comparable to Java since .NET was basically cloned feature for feature from Java with some additional features added.

    --
    Mod me down, my New Earth Global Warmingist friends!
  23. Re:Inflamatory headling superceeds mundane content by ByOhTek · · Score: 2, Informative

    .NET is Microsoft's implementation of it's CLR (Common Language Runtime). In general anything CLR tends to be referred to as .NET.

    Mono is an open source implementation. It runs on Windows, MacOS, Linux, FreeBSD and I believe I've even seen it for HPUX. There are probably other platforms. In my experience, if your platform has a libgdi+ library available for it, mono will run most .NET apps written in Visual Studios 2003 and earlier. I'm not sure about later MS dev environments. I also don't know if libgdi+ is needed separately in all environments or just FreeBSD.

    --
    Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
  24. Re:Inflamatory headling superceeds mundane content by Jerry · · Score: 3, Insightful

    Five months ahead?

    How can you maintain and guarantee compatibility? Divination, or do you actually work hand in hand with Microsoft .NET developers?

    And, has Microsoft added ASP.NET and its other IP to the EMCA 334 & 335 specifications, so that you can legally add them to MONO?

    --

    Running with Linux for over 20 years!

  25. Re:sonofaspellingfail. by Jurily · · Score: 2, Insightful

    Don't worry, "headling" still sounds smarter than the whole .NET vs. Mono debate.

  26. Re:Good News by Anonymous Coward · · Score: 2, Interesting

    I don't work for the enjoyment of it. I've never had a job I wouldn't rather quit to go read novels all day. I believe most people, if they were being honest, would agree with the statement. That makes us both whores. The only people who work who are not whores are those who are independently wealthy or retired, and work merely for fun or to stave off boredom.

  27. Re:Inflamatory headling superceeds mundane content by stoolpigeon · · Score: 4, Insightful

    You thought wrong.

    First parties posting is one of the strengths of the dot.

    --
    It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
  28. What I thought Miguel said by einhverfr · · Score: 2, Insightful

    was that Mono would have a lot of competition if it wasn't for the implicit patent threats coming from Microsoft. IOW, he was complaining that JVM technology had come a long way due to open policies from Sun and that .Net runtime engines had not enjoyed the same benefits. I think he is probably right there.

    What I didn't hear him saying was that Mono was a bad project, risked patent infringement claims, etc. There seemed to be some concession on the patent issue but it seemed overblown.

    At the same time this summary, suggesting that the communication was handled "irresponsibly" seems no closer to the mark. I can see why people got the impression they did and I think it was a reasonable one.

    Things could use everyone stepping back and taking a few deep breaths :-)

    --

    LedgerSMB: Open source Accounting/ERP
  29. Still missing the point... by dclozier · · Score: 3, Informative
    Microsoft's patent pledge is a bit shallow. Bradley Kuhn wrote:

    A careful examination of Microsoft's Patent Pledge for Non-Compensated Developers reveals that it has little value. The patent covenant only applies to software that you develop at home and keep for yourself; the promises don't extend to others when you distribute. You cannot pass the rights to your downstream recipients, even to the maintainers of larger projects on which your contribution is built..Further, to qualify for the pledge, a developer must remain unpaid for her work. Experience has shown that many FOSS developers eventually expand their work into for-profit consulting. Others are hired by companies that allow or encourage Free Software development on company time. In either situation, Microsoft's patent pledge is voided for that developer..Even if the patent pledge were to have some use aside from these problems, our community simply could not rely on it, since Microsoft has explicitly reserved the right to change its terms at any time in the future. A developer relying on the pledge could wake up any day to find it revoked. She'd have to cease development on her non-commercial and (mostly) non-distributable modifications that were previously subject to the covenant.

    I'm sure that as long as companies follow in Novell's footsteps they'll be fine.

  30. Re:Inflamatory headling superceeds mundane content by nschubach · · Score: 4, Funny

    The slash however is a slippery slope.

    --
    Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
  31. Re:And what have YOU done for Free and Open Source by Jason+Earl · · Score: 3, Insightful

    What's more, Mono is undeniably Free Software, and it follows the grand tradition of GNU software in that it re-implements someone else's proprietary software (while mixing in its own completely Free Software extensions).

    I am by no means a fan of Mono, but I fail to see how it is any different than gcc or the many GNU utilities that are basically work-alikes of any number of proprietary software products. Cloning commercial software products is hardly a new theme in Free Software. What is it, precisely, that makes Mono a special case.

    The difference, apparently, is that Microsoft is especially evil.

    The problem with that, of course, is that Microsoft is not really that particularly evil. Especially compared to AT&T or IBM in their respective heydays. Sure, patents have changed the game somewhat since the early days of UNIX, but Free Software's defense against patents has always been the same. Pretend that they don't exist until threatened, and then write the functionality out of the effected software. Mono is not appreciably more vulnerable to attacks from Microsoft than the Linux kernel, or any other major piece of Free Software.

    So really, why all of the hate?

  32. Re:-1 Misses the point by binarylarry · · Score: 4, Informative

    Java's virtual machine (specially Sun/OpenJDK) is much more advanced than Python's (CPython).

    Python takes a bytecode and then executes the one or more native instructions it takes to fulfill the purpose of the bytecode instruction. And that's basically all it does.

    Java takes the bytecode instruction and compiles into a native format and uses thats for future executions. In addition, it does many other types of optimizations to increase the execution speed. You can run Java in a purely interpreted mode like Python does, pass the -Xint argument on the command line to the java instance. You'll notice it's 10000x slower than the optimized execution paths.

    Java's class library is primarily Java code, whereas Python wraps native libraries for much of this work. Both methods have their pros and cons, but it means Python can be prone to more issues regarding different system libraries, etc. Since Java provides it's own virtual platform with most of the code in Java, you don't have these issues as often.

    Java also allows for true threading, whereas Python threads are limited by the global interpreter lock preventing you from getting real performance gains from asynchronous execution. You have to resort to multiple python processes to take advantage of multicore processors for example.

    --
    Mod me down, my New Earth Global Warmingist friends!
  33. Re:Inflamatory headling superceeds mundane content by Timothy+Brownawell · · Score: 2, Funny

    IIRC Wikipedia also says you can only write about things you don't actually have any real knowledge of, because learning about something necessarily means you acquire some biases about it. Slashdot can be pretty dumb at times, but I don't think we're quite that bad. Yet.

  34. He HAS Admitted Defeat by segedunum · · Score: 4, Interesting
    Whatever way you cut it, this is an admission of defeat and it has been exactly what everyone has complained about regarding .Net and the nonsense surrounding Mono for years. De Icaza has sought to paint over it at every single turn until now. Maybe the penny seems to have finally dropped:

    "The most important part is that Microsoft has shot the .NET ecosystem in the foot because of the constant thread of patent infringement that they have cast on the ecosystem. Unlike the Java world that is blossoming with dozens of vibrant Java virtual machine implementations, the .NET world has suffered by this meme spread by Ballmer that they would come after people that do not license patents from them.

    Sun on the other hand said from day one: we will not sue you over patent infringement if you implement your own Java. Google does something similar with their APIs and Google's Wave: they are giving everyone access to their stuff.

    As the only implementor of the ECMA standards outside of Microsoft, I sure would have hoped that they had given rights to everyone to implement. They would still be the #1 stack, but it would have encouraged an ecosystem that would have innovated extensively around their platform.

    Instead, people went and innovated on Java or other platforms that might not have been as advanced as .NET, but at least they were not under Microsoft threat."

    It's very clear. The part in bold I find most damning. This indicates that he knew all along that you couldn't create an open source implementation of even the CLR without permission from Microsoft. There is a lot in here, but people like Bruce Byfield obviously havent read it properly. He's tried top backtrack and cover up a bit by saying that it's all nothing, but it most certainly is something.

  35. What about him and Novell? by Ilgaz · · Score: 2, Insightful

    I think he and his gang along with that pathetic dying company should leave Gnome, Linux alone. No more trickery to insert Mono to Debian, flagship open source Linux which is (was) like a manifesto of open source philosophy until it got that stupid notes app.

    Would they agree on that?

  36. Re:Inflamatory headling superceeds mundane content by shutdown+-p+now · · Score: 2, Informative

    Most new features have been announced on PDC'2008. Since then, there has been a public beta of VS2010 / .NET 4 in May 2009, a second one in October 2009, and RC in February 2010.

    It's still impressive that they have implemented it all in slightly over a year, but there is no mystery here.

    There haven't been any updates to Ecma-335/335 so far. This doesn't preclude Mono from having an ASP.NET implementation, though - in fact, it's probably the single non-Ecma library that Mono has the best (most compatible etc) implementation of, and had for a while.

  37. Re:And what have YOU done for Free and Open Source by Chris+Burke · · Score: 3, Insightful

    I am by no means a fan of Mono, but I fail to see how it is any different than gcc

    Ah well that makes sense. Here it is in a nutshell:

    Gcc is, as far as anyone is aware, free of all patented technology, in particular patents owned by companies hostile to free software.

    Mono is most definitely encumbered by patents owned by a company that is very hostile towards free software, and has been recently becoming more vocal about alleging patent violations in Linux and threatening legal action.

    Mono is not appreciably more vulnerable to attacks from Microsoft than the Linux kernel, or any other major piece of Free Software.

    Yes it most definitely is! Because the vulnerability is not hypothetical, it is not a made-up FUD tactic. It's plain as day and undeniable that these patents cover things in Mono, and it is not a simple matter of recoding if MS ever becomes aggressive. There are aspects of the framework that simply cannot be implemented to spec without running into these patents.

    Microsoft has no interest in anything cross-platform excepting those that are owned by MS. They have promised not to enforce patents against Mono, but this is not a legally binding promise. The only reason they have to let Mono exist is to waste the time of Linux developers, and to encourage adoption of a framework that is ostensibly cross-platform but can be instantly made Windows-only any time they want.

    Oh and I think you're wrong. MS is just as evil as IBM and AT&T. Main difference is that today MS only controls the software while IBM controlled both.

    This is absolutely a time bomb and MS is just waiting for the right moment to set it off.

    --

    The enemies of Democracy are
  38. Re:And what have YOU done for Free and Open Source by Jason+Earl · · Score: 3, Insightful

    If the danger to Mono is so obvious, then please point out the patent numbers that Microsoft owns that would apply to Mono (and that don't, at the same time, apply to Free Software tools like OpenJDK, or gcc). Additionally, you should only use patents that don't apply to the ECMA specification.

    What? You don't have access to such a list? Imagine that! My guess is that this is because (to my knowledge) no one has come up with such a list of patents. It is possible that you have access to such a list--in which case your accusations could *potentially* stop being FUD. Until then, however, you have no evidence that Mono is particularly vulnerable to attack from Microsoft.

    Microsoft has already stated that it believes that Linux (for example) violates hundreds of its patents. In fact, it has even signed patent deals that supposedly cover Linux. Patent attacks on Linux are definitely not FUD. Should I stop using Linux as well?

    If Mono is a trap, then it is quite likely to be the stupidest trap in the history of the world. At the very best Microsoft could force the Mono developers to be less compatible with .NET. Since Mono is not particularly compatible with .NET in the first place this is hardly a huge threat.

  39. Re:And what have YOU done for Free and Open Source by Chris+Burke · · Score: 2

    And Mono is, as far as anyone is aware, free of all patented technology.

    Or have you found a patent that covers .NET? I haven't. No one else I've asked has. Have you?

    Are you fucking kidding me? Are you only just hearing about Mono today? Is everyone you know equally clueless, or did you just never think to try maybe checking the Mono website itself which informs you that it implements patented technology. It's always been known that Mono is not free of patented technology, Miguel has never claimed it was free of patents, he always admitted that it was not.

    Oh and yeah before you get to it, we've also known about the Community Promise for a long time and discussed its problems too. Specifically, note that this "irrevocable" promise only applies to things that implement a specific version of the standard, and even then only to the extent that they comply with the standard (as decided by Microsoft), and that any future standard may or may not be covered by the promise.

    In other words, at any time they want, MS can decide your implementation doesn't comply, or release a new version of the framework that you are no longer able to comply with and cannot implement without exposing yourself to patent claims.

    It's embrace-extend-extinguish like usual, only this time MS tricked part of the Linux community into doing the embracing.

    --

    The enemies of Democracy are
  40. Re:And what have YOU done for Free and Open Source by Chris+Burke · · Score: 2, Informative

    So a half-assed internet search uncovered a patent that covers the architecture for networked applications in .NET. And that's not good enough for you? How did that go again? "As far as anyone knows, Mono has no patent issues... except the one I found in two minutes of googling. But I'm sure that's it."

    Yeah whatever.

    I'm not doing "diligence" because I'd never set my foot in that bear trap in the first place.

    --

    The enemies of Democracy are
  41. Re:And what have YOU done for Free and Open Source by fejjie · · Score: 2, Informative

    Wow, you fail at reading comprehension. Miguel has never claimed that Mono *doesn't* infringe on patents because he can't be 100% certain that it doesn't, it's not the same as knowing that it *does*.

    No one has been able to point us (the Mono team) at a single patent that we may infringe. Not one. You'd think, with all the rabidly anti-Mono trolls such as yourself, that one of you, after 9 years, would have come up with at least 1 solid patent infringement claim, but no.

    Same old vague hand waiving claiming we infringe patents that you can't point to but just *know* exist. Sorta like some people claim to *know* that God really exists, or like many children believe with all their heart that Santa Clause really exists.