Slashdot Mirror

← Back to Stories (view on slashdot.org)

Technology Review Profiles Miguel de Icaza

Posted by simoniker on from the de-impressive dept.

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."

4 of 231 comments (clear)

  1. Re:You can't be both. by JanneM · · Score: 4, Informative

    [...] de Icaza took the interview as an opportunity to lecture managers on why Microsoft should abandon its multibillion-dollar business model and embrace open-source programming. Not surprisingly, de Icaza wasn't hired.

    The blurb here makes it sound like he was begging on his knees for them to take him on. Not quite what the article describes. He's not the least "confused on what side he's on".

    --
    Trust the Computer. The Computer is your friend.
  2. Re:Miguel has told you why by miguel · · Score: 4, Informative

    Some languages map very nicely to the JVM or the CLR
    (the same developer that did Jython now has
    a very fast implementation called IronPython that
    was unveiled and demostrated at OSCON).

    The problem is with languages that require pointers:
    Fortran, C, C++ and some extra support is convenient
    for some functional languages that the CLR
    provides.

    I mean, nothing really ground breaking, but the
    CLR had a chance to learn from Java's limitations.

    The new MS C++ compiler generates pure CIL executables
    when using the /clr flag which is a very convenient
    way of integrating existing C/C++ codebases with
    managed codebases.

    Miguel.

  3. Re:hrm... by miguel · · Score: 5, Informative
    That is why Mono implements two stacks:

    http://primates.ximian.com/~miguel/tmp/two-stack s. png

    One is the Microsoft compatible one.

    The other one is where we are pouring our energies:
    An ECMA core with the following on top:

    • Gtk# to build GUI applications.
    • Simias: to write collaborative applications.
    • iFolder: to synchronize your file system and integrate into your high-end applications.
    • Beagle: a platform to provide searching and contextual information at any moment.
    • Novell.Ldap: Focus on open standards for directory services.
    • Mono.Data.*: The API to access open source databases.
    • RelaxNG: Microsoft likes XmlSchema, it is older, but RelaxNG is cleaner and simpler, and we have a stack to use it.
    • IKVM: We integrated natively with Java.
    • IronPython: we can run your Python code.
    • Cairo bindings: to provider advanced rendering.
    • Tao: OpenGL/SDL APIs for your applications.
    • Gconf#/Dbus#: APIs to access the configuration and bus systems on modern desktops.
    • Gecko# to integrate Mozilla into your apps.


    There are quite a few of other open source stacks
    for the ECMA CLI today that range from research
    to practically useful.

    Miguel.
  4. Re:hrm... by miguel · · Score: 4, Informative

    No, today we do not have Windows.Forms implemented
    (I should update that graph with the latest version
    where we point that out).

    Windows.Forms will be available in a few months.