Domain: tirania.org
Stories and comments across the archive that link to tirania.org.
Comments · 159
-
Trust Microsoft.
Miguel de Icaza: Mono BOF Proposal Turned Down By Microsoft For Second Year Running?
"At the last PDC," Miguel de Icaza (pictured) notes, "the Mono BOF had the largest number of votes when half the spots were still available and it got dropped out of the list." Now it seems that history is about to repeat itself.
Writing, in his blog, of last year's disappointment, he explains:
"When I asked the various people in charge what happened they kept pointing fingers at someone else until it reached full circle. Nobody could tell me why the most voted BOF proposal did not get selected. I would be happy with an honest answer even if it is "We do not want to promote open source/Mono/Novell" instead I heard a number of variations on "The problem is that `New frontiers for 6502 assembly language in the copy-editing industry had more votes'" (it didnt)."
This year's PDC, de Icaza fears, "is looking just like the last one. So it is time to get ready for a Mono meeting like we had the last time: in the middle of the hallway."
Very telling entry from Miguel's own blog.
What's on display here isn't even remotely close to a cooperative spirit to further a community standard. It is more of a Cold War.
ECMA? Who cares... ECMA trying to set the direction of C# and CLR is like steering a truck with a flea. -
Re:SummaryYes, as far as I know, there are no plans to clone "WinFX" at this point for Vista compatibility.
WinFX is far from required for "Vista compatibility". Basically no applications will use WinFX when Vista is released, and I have to wonder how many Windows developers are actually ready to jump ship from unmanaged C++ to .NET and WinFX. The new WinFX development models with e.g. Windows Presentation Foundation and XAML for UI development, etc. are totally incompatible with current C++ applications. It feels like several years ahead at the very least.
As for the Windows.Forms namespace, it's well underway actually. In the November 2005 status report, word is:Windows.Forms is the only piece that is holding us from officially renaming Mono to Mono 1.2, it is still missing a few features. Our plan is to complete the missing features by the end of this month and then move to bug fixing and testing open source our publicly accessible Windows.Forms applications. We are planning on spending three months on bug fixing at this point.
This hardly sounds too unattainable to me.
And before anyone asks, no, Windows Forms 2.0 support isn't required for "Vista compatibility" either. -
Re:windows application interoperability
more info about java integration
http://tirania.org/blog/archive/2005/May-17.html
Am I the only person who reads Miguel's blog?
http://www.ikvm.net/
He posted about this almost a year ago. I've been using monodevelop on FC and SuSE for quite some time. It's gotten alot more stable. You all can compile java to mono IL through IVKM. -
Re:I don't want to be stuck with one..
It seems like the only people who have any interest in C# are
The Mono project is actually gaining some momentum and it's been progressing quite nicely.
Novell would hardly have supported it this much if there was no interest in cross-platform .NET languages. -
A few thoughts.
I added a few of my thoughts on my blog:
http://tirania.org/blog/archive/2005/Dec-28.html -
Re:Mono is DOA, dude
What?
Novell has adopted it as their .NET runtime, and there was a huge update regarding the future of mono only a month ago, which can be found here. I won't even get started on how Mono 1.1.10 was released only a month and a half ago. -
Google Earth for Linux - almost exists
NASA's Worldwind software is similar and is a
.NET app,
so there's a Linux version for Mono underway that I'm told
mostly works already (it's mostly a reimplementation using the
same data).
More info and pretty screenshot in Miguel de Icaza's blog:
http://tirania.org/blog/archive/2005/Sep-30-1.html -
Re:how about an alternate location?
-
A lot of historical info.