Looking for Linux? See our new home at SUSE.com
Looking for Identity, Security & Governance or IT Operations Management? See our new home at NetIQ.com
+ Novell Services Overview
+ Novell Partners Overview
+ Novell Communities Overview
+ About Novell
+ How to Buy Overview
Request a Sales Call
11 August 2006 - 8:29pm
Submitted by: coolguys
I don't usually link to Microsoft - this time is an exception.
There is a fascinating interview on Microsoft Technet Port 25.
Here's the link - http://port25.technet.com/archive/2006/08/11/Let_2700_s-talk-Mono_3A00_--Sam-interviews-Miguel-de-Icaza.aspx
Submitted by flyingGuy (not verified) on 12 August 2006 - 7:35pm.
Hmmm what to say....
I can't really see how Mono will be a stable and reliable project. .Net is an MS Product and one only has to look back to IMAPI to see how MS has screwed the rest of the world.
I can see Mono working, for a while, until MS simply changes something in .Net, releases it the automatic update flow and Mono is dead in the water until they can reverse engineer what MS has done.
The entire underlying principle of .Net, is just .Silly. At some point we are all going to have what, a quad processor machine, with 40 gigs of RAM JUST to handle the 3,456.289 layers of API until we actualy accomplish something?
I understand what they are trying to do, but I will never trust MS to do anything that is in the interest of ANYONE except MS. I predict if they sense the least amount of control slipping, they will simply change the unerlying API just enough to break Mono.
Mysteriously, all of the windows native .Net will just keep on gobbling memory and CPU cycles and the rest of the world will just tag along writing horribly overbloated code.
© 2013 Novell