Slashdot Mirror
Technology Review Profiles Miguel de Icaza
prostoalex writes "Technology Review has a feature story on Miguel de Icaza, currently Novell VP of Product Technology, but more known as the leader of Gnome and Mono projects. Miguel is the man Don Box would like to see joining Microsoft for his "amazing amount of raw energy". If you read through the Technology review article, you will see that de Icaza was actually turned down by Microsoft at some point."
I met Miguel, like, back in '98 at a conference in Mexico. Yes, Linux existed there back then!
We chatted and I quickly found he was more than just a Rob Malda or Rusty Foster, guys who talk the talk and get all the fame but can't back it up when it comes to lines of code per hour counts.
Miguel simply AMAZED me with his knowledge and skill. He ever opened up a digital projector and messed with the PROM or jumpers or something and fixed it within 20 minutes, just in time for his talk.
de Icaza is nothing short of amazing. I DO however question his judgement to kind of jump into the MS camp with MONO/.NET emulation, but I know that since he's smarter than me he must be doing the right thing.
If you liked my post,
I'd like to thank Miguel for his contributions. I'm a gnome user, and it is quite nice. What I don't get though, is why he seems absolutely fascinated with the boys in redmond. He reimplements Outlook, and now he's reimplimenting their reimplimentation of Java. Why not get behind an OSS implementation of the original ala kaffe or gcj, or push the OSS own Parrot?
Rip on Miguel as you like, but recall, this is a man that wants the linux desktop to prosper, regardless of what fanboy, ub3r wannabies latch on.
I have no desire to rip on Miguel; however, I think Miguel may have underestimated Microsoft.
My opinion is that .NET is a trojan horse: The "best" and "most up-to-date" implementation will always be on Windows, which will give Microsoft a great deal of marketing strength, even if Mono can run a large number of .NET applications (which seems a long ways off: Windows.Forms isn't "standardized" by ECMA, and it's very Windows-centric. Mono needs Windows.Forms in order to run GUI-based .NET applications).
And if the Linux/Mono combo ever becomes a serious threat, Microsoft can just beat Mono into submission with a fist full of patents.
Even though Java is proprietary, Sun has bent over backwards for years to get the community involved and keep the community involved. The ubiquity, robustness, and maturity of the Java Virtual Machine makes Java ready right now for what Mono may be ready for some day.
Don't be paranoid, but at the same time, don't dismiss Microsoft's pattern of abusive behavior over the years. Before you commit to Mono, think through all the alternatives first, and be sure you're not opening the city gates for a trojan horse.
These are baseless accusations. I would suggest you keep the conspiracy theories to yourself unless you have some evidence to back them up.
Maybe you are actually someone hired by Microsoft to spread FUD on slashdot!
Miguel's a leader of the community who deserves our respect. I think it's become clear over the years he could have made as much money as he wanted but chose to do what he felt was right.
A lot of people denigrate Miguel as being a "Microsoft fan."
That's not fair. What he is, is a realist. The fact is that as long as Microsoft has a vast majority of the desktops out there, any competing system has a choice: between creating their own 31337 world where only the initiated may play, or instead creating systems that work and play well with others. By paying close attention to what system and paradigms users are used to - that is to say, that Microsoft ships - Miguel helps furhter the rapid adoption of Linux as a viable Windows alternative.
Why he is imporant is not just that he realizes this, but that he does something about it. Real hackers write code for their beliefs, as he does.
http://primates.ximian.com/~miguel/tmp/two-stac
One is the Microsoft compatible one.
The other one is where we are pouring our energies:
An ECMA core with the following on top:
There are quite a few of other open source stacks
for the ECMA CLI today that range from research
to practically useful.
Miguel.
For me it is difficult to put my finger on exactly what has hampered Java's uptake in the general open source community.
/usr/share, libraries in /usr/lib and so on, why can't Java?
It's unlikely to be only one reason. These issues are big, complex with many aspects, and every developer that has made a choice in this field probably have their own unique blend of reasons.
For me, it has come down to a few things, but these hase tended to change as well.
I started playing with Java looong ago, like 1995ish, and actually wrote a small app as part of a summer job (which didn't really go anywhere). It was pretty horrible at the time. A big problem was that we were doing client-side apps, with an UI, and with Java and its UI libs, our then modern machines ended up with the performance of a CBM64, but with far uglier user interface. I still have dreams about that experience after a night with too much beer and rich food.
Today, the performance is better. Using Swing (is it? I mix them up), it tends to look better as well. But: any UI is still uncoupled from the rest of my desktop. I have my nice AA fonts everywhere - except in a Java app, which uses its own font settings and no AA. Controls, cutting and pasting and so on also reinforces that the app is just a free-floating guest on my machine and is not integrated one bit. Also, the runtime takes a _lot_ of resources - on disk and in memory. There sould be no need for that, really - all other VM:s I have (mono, perl, python) seem far less resource hungry.
Oh, and the install is also "too good" for my machine, and plonks down itself in its own private directory, not deigning to play nice with the rest of the machine. If all my other apps can have common resources in
OK, this sounds like a litany. It's not that bad, but you wanted to know why people aren't enamoured with Java the way they seem to become about mono, and this is my personal (partial) answer. In short, I write a GTK# app in mono, and it feels like a natural part of my desktop. I write it in Java, and it feels like an intruder.
Trust the Computer. The Computer is your friend.