Miguel De Icaza On Mono, Moonlight, and Gnome
Knuckles writes "Austrian newspaper Der Standard continues its recent series of in-depth interviews with free software developers. This time they sat down with Novell's Vice President of Developer Platform, Miguel de Icaza of Gnome and Mono fame. The interview was conducted at GUADEC (GNOME Users' And Developers' European Conference).
Miguel talks mainly about Mono 2.0 and .Net 3.5 compatibility, enhancing the collaboration with Microsoft over Silverlight ('Moonlight' in Mono), and the larger political situation of Mono and Moonlight. When the interviewer asks whether Moonlight is only validating Silverlight on the web, Miguel gives a quite detailed answer that includes a possibly well-deserved swipe at Mozilla ..."
Looks like Miguel still pimping a marriage with Microsoft. Dude, she likes country and he likes rock-n-roll! Seafood vs. burger and fries. He's frugal, forward looking and she spends money like a drunken sailor! More importantly he just wants some freedom and she wants to tie him down. Let it go!
"de Icaza: I hope so. It might end up that at some point Microsoft just open ups .net"
LOL
I just find it's terribly dumb to let both your specification and the reference implementation to be under the control of your worst enemy.
I love Gnome and I understand Mono is a somewhat simpler (than C++) way to build programs for it, but is it really necessary?
As for Silverlight... Yuck.
http://www.dieblinkenlights.com
MS has made it clear that they want to kill OSS. So Miguel decides to make an OSS alternative to Silverlight with MS's help, unfortunately, MS will add in proprietary features once this halfway kills flash, and the reference implantation won't be the OSS Moonlight, it will instead be MS's proprietary Silverlight.
Taxation is legalized theft, no more, no less.
1. One has to give some credit to Miguel for thinking big and at least attempting to do it. The way he's doing it is perilous and I can see why some in the OSS crowd fault the guy. The odds are working against him. Strongly so.
2. He's convinced Novell this is something to spend/make money with. He's got a 40-person head count and it is totally unclear to me how Novell ***makes money**** on this to support such a large dev team. If they turned themselves into a 40-person contract dev group, I don't see customers clamoring for a dual-platform solution.
Even if his projects are widely adopted, there's no way I can see that Novell can make money at it. Which still makes Novell operating in run-off mode until the last netware(?) customer quits.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
As this blog post explains, while the current software patent situation exists, Mono is an unacceptable risk.
He definitely has a point with A. and some with B. (though it's a matter of opinion), but C. is just FUD. He obviously doesn't understand JavaScript (not the DOM, JavaScript is not just the DOM). JavaScript can produce very elegant code if you know what you're doing. I'm sure you can get some pretty nasty C# spaghetti code too (though it may not be as likely). I doubt that any language will replace JavaScript any time soon. All the different browsers would have to support whatever replaces it almost simultaneously. Flash is getting close, but it seems the community is treating Silverlight as a "me too" offering from MS. /rant
His comments about Mozilla are pretty interesting. I appreciate the work on Mono that they've been doing, but it's still strange to be at the mercy of MS whenever they make a change to their setup. That alone will leave Mono/Moonlight at least one step behind and could be used as an argument for only using Windows.
Actually, although the Flash IDE is closed-source and proprietary, the SWF file format is now a published specification which others are free to implement.
Adobe did this years ago with PDF, and didn't take long to do so for SWF once they bought Macromedia. They want everyone using their formats, and to then compete based on the quality and branding of their authoring tools. It's a good business case in my eyes -- make the pie bigger by opening the spec but keep most of the pie yourself by making the best-known implementation that the most people know how to use.
To compare that with anything Microsoft has ever done, the executable format for Windows is the best example. To get more programmers targeting Windows, allowing more compiler makers into the market easily was a must. If you can only compile programs using the OS vendor's compiler, that feels very much like lock-in. By getting competing compiler and assembler products supporting their OS quickly made it easier for developers to decide to target the platform in its early days.
OOXML, albeit a contentious, oversized, and and only partially specified format, is an example of Microsoft trying to do some of the same things. They're trying to get people who believe in open, competitive file formats to use a format they have a competitive advantage in producing and editing. With Microsoft's past (and some of the gotchas in the spec itself), it's easy to see how that advantage could be kept through much chicanery.
However, the Adobe's got a pretty good record of allowing anyone to come along and make use of the Photoshop save format, the PDF publishing format (which is itself based on PostScript), and allowing JavaScript and ActionScript (both based on the ECMAScript standard, after all (which is based on earlier versions of JavaScript)) to interact cleanly. Now that SWF as a spec is published, it's difficult for honest people working with Microsoft technology to be judgmental about openness.
"I hope so" refers to Mono becoming the officially sanctioned .Net standard for Linux -- not that de Icaza hopes Microsoft would open up .Net. If you actually read the very next question in the article (I must be new here...), you'd have seen where de Icaza said:
In the meantime - I really don't think they are going to open source .Net.
-- they are talking about the possibility of Microsoft pulling a Sun/Java thing, and if the open-source effort would have been wasted as a result. The answer is "no, but I don't think they would open-source it anyways".
But imagine Flash if even though it displayed banner ads just fine, it couldn't play YouTube and some games. That's exactly what could happen with Moonlight, sure it is OSS but it is useless.
Taxation is legalized theft, no more, no less.
Awesome track record? I'm sorry, I must be living in an alternate reality. So MONO is now being used interchangeably on Linux and Microsoft platforms like Java is? Like he planned all along? So MONO has gained mass adoption and mass acceptance and has been embraced by Microsoft and they are now allowing them to .NET conferences where they were continually denying them from showing?
... DeNial. You and Migual must shop at the same store.
Wow. This new reality you live in smells vaguely of that new fragrance
This is my sig. There are many like it but this one is mine.
http://www.gnome.org/~seth/blog/mono
As this blog post explains, while the current software patent situation exists, Mono is an unacceptable risk.
What makes Mono an 'unacceptable risk' but allows Wine to become one of the most often praised open source projects on Slashdot?
Wine can be used to run those few windows apps for which you do not have no linux replacement, under linux. Mono is a development environment which could be used for just about anything... what if gnome, or some important gnome apps, got ported to Mono, and the day after Microsoft comes up with the bill?.. or with usage restrictions of some kind... Please read the link in the parent post, before replying... Here it is again:
http://www.gnome.org/~seth/blog/mono
the PDF publishing format (which is itself based on PostScript)
PostScript is the best example. Adobe wrote the first standard and implementation. They published a later version of the spec before they had an implementation and were beaten to market by a competitor. I don't know what, if any, market share Adobe still has for PostScript implementations (RIPs), but they certainly get a lot of money from the desktop publishing market that releasing PostScript helped to create.
I am TheRaven on Soylent News
Try again. I'm only getting maybe 10% more CPU use by opening a tab for CNN.com on Firefox here with the latest player, and that's under 64bit Kubuntu, which runs the Adobe flash player in nswrapper.
My blog. Good stuff (when I remember to update it). Read it.
In creating .NET, Microsoft correctly recognized a problem they had: their existing cross-language development tools such as COM had a high learning curve and were clunky to use. Their offerings for developing an application were C, C++, or Visual Basic. Working with these components and making them inter-operate highlighted the desire for a powerful, "real" object oriented, garbage collecting, managed runtime. Say what you want about Microsoft's intentions, .NET is a step in the right direction for them. And if Linux developers feel the features it exposes are better to work with in some cases than Java (I happen to agree with that), there's no shame in adopting them.
Yes, potential patent issues make it so there is some risk involved. If MS is smart they'd realize that would severely hurt their image. On the other hand, do they really make legal decisions without considering their own potential problems, like running afowl of antitrust law, or being seen as more monopolistic than they are seen as today? Nevermind that being a monopoly would make them liable to lose billions of dollars, but also, they have an image problem already, and they probably don't want to make it worse.
But let's ignore that patents, or what company .NET comes from. The technology is pretty solid. It was the right thing to do to go beyond their existing technologies like COM. It's a pretty good answer to Java and addresses some of its shortcomings well. It also has more than one supported language. They say that pretty soon, it'll have inbuilt Python and Ruby too.
In creating Silverlight, MS recognized another area that could use some work: namely, flash sucks. It looks pretty doubtful that we'll see it adopted at this point, but if it does, it'll be good that Moonlight will have source code available. Yes, there are free/open projects that do Flash today, and are working on reverse-engineering, but you just know that they'll come out with more changes next week. If Moonlight is working with MS to provide real inter-operability, I think that's a good thing.
The only reason I usually turn off Flash on sites other then some game sites or YouTube, is because the Linux Flash player is just so crappy. I have a decent enough /etc/hosts file that blocks 98% of the ads, but if I leave Flash on, Firefox's CPU shoots to 80% just displaying a banner ad. Thankfully, I downgraded to an older version and it doesn't do it as much.
Ehm, this is not the linux flash player as such, it's the flash player, period. I get the exact same problem on some sites in windows. Also downgrading flash is a seriously stupid thing to do right now, as the recent vulnerability they discovered leaves you wide open to attack. (and it has been spotted in the wild, though generally targeted at windows)
Translation: We'll try to make the whole desktop dependent on a MS standard.
The increasing openness of these guys?
You meant MS changed the whole definition of what is part of .net to include stuff not covered by OSP or that are not portable? Shocker.
Moonlight is going to require a proprietary addon in order to actually interoperate with silverlight, pretty sweet.
For every distribution, also x86, x86_64 and PowerPC. In fact we are going to provide binaries for BSDs, for Solaris - both on SPARC and Intel.
Same old, you'll have to download them from MS and only MS, and SLED will be the only distro one able to ship them. Oh, it looks like Icaza actually confirms so in page 2.
hahahahahha
As a hacker you get Microsoft, Microsoft, compatibility to Microsoft languages, and Microsoft. And beating javascript with Microsoft.
Specially after the free, false advert of 'silverlight works in Linux' thanks to moonlight.
Typical MS fanboyism from Icaza
Diverting attention are we?
Icaza here's the deal: AT least FLASH is NOT FREAKING MICROSOFT! Don't you get it? call it a double standard if you want, just missing all the previous record of Microsoft's anticompetitive actions and the clear intent to take over the world with .net and how Mono makes Linux threated by it... It is getting ridiculous.
Mozilla is evil therefore we'll help poisoning the web with Silverlight, fuck open standards.
Copyright infringement is "piracy" in the same way DRM is "consumer rape"
They have an awesome track record of coming up short. Like the winforms support that is still coming up short! He himself stated in the interview that moonlight will be like a "light version" of silverlight. So us linux desktop users are supposed to remain first-class citizens on the web by using a second rate, braindamaged implementation of a new, unproven web technology by Microsoft of all places? Hah!