LinuxWorld: Business, Business and More Business
Clarkson University wins a server from IBM. Sun is bringing embedded Linux to its UltraSparc IIe processors. Wired has an overview of LinuxWorld, talking about how it's all business and the joy is gone; and so does Internet.com; and so does Newsforge, which also has a story about LinuxWorld in Paris. The Register has a lengthy interview with Miguel de Icaza, in which he notes "Gnome 4.0 should be based on .NET".
I also got to experience the feel of the old days, having brought my TiBook for a demo system. There were quite a few Apples in evidence, and I proabbly spent more time talking PPC Linux than I did KDE. The PowerPC Linux crowd continues to have all the community feeling that Linux as a whole lost when the gold rush started. Curiously, the Apple guys who stopped by the booth seemed completely uninterested as all the Linux guys drooled over the TiBook.
What I'm listening to now on Pandora...
Answer the following questions, truthfully:
1) If Microsoft changes the spec for C# or CLI, can ECMA deny the changes?
1a) If they can deny the changes, can Microsoft still call C# "C#"?
2) Are C# and the CLI completely free of patents?
If the answer to 1) is false, then at any time MS can change the spec on what C# is, and leave Miquel to play catch-up.
If 1) is true and 1a) is true, again MS controls the table.
If 2) is false (it is, by the way...) then at any time MS can jerk Miquel up short and deny everybody the right to use the code without paying them a royalty (think Unisys and LZW).
I assure you, I am neither a troll nor an idiot - rather I am a person who can see beyond "that's cool" and ask myself what the downsides are.
www.eFax.com are spammers
"With .NET once an API is published it's available to all programming languages at the same time."
.NET MYTH: that you can just willy-nilly plug in existing languages in the CLR nirvana. He has become one of those .NET fan boys who show up touting that .NET supports over twenty programming languages.
.NET are a pile of large stinking COW dookey!
.NET. What are the hard realities:
.NET support for the .NET versions of languages do not. Programmers don't want to work with 80 percent of the features of their chosen language simply because the .NET version of the language doesn't support it. They also don't want to deal with compatibility problems arising with FunctionA() acts differently when run under the C++.NET as opposed to the native C++ environment.
.NET universe impose straight jackets on languages that no programmers will want to deal with. Programmers don't want to be confined to using a limited set of types and classes just so their program can function in the CLR. Should I even mention the compatibility problems that existing code will have within the .NET sandbox?
With comments like these, Miguel has really lost it. Perhaps he never had it to begin with.
He appears to have this entirely fantastical idea that when Mono reaches 1.0, we will be able to just plug in the existing C, C++, Perl, etc code bases into it and, WAMMO!, instant cross language, cross platform code. I can understand his frustration with updating Gnome language bindings. However, I think his mind has snapped from doing that kind of work.
He has bought into the central
Note to Miguel: the cross languages promises of
Programmers don't like half assed solutions to problems. And that is just what Perl, Python and name-your-favorite-language are inside the world of
(1) Languages evolve. The
(2) The Common Type System and Common Class Libraries of the