To read all comments associated with this story, please click here.
The problem is that C and C++ are obsolete languages that are a pain to work with. Thats like saying why use python when we have a perfectly good fortran?
And mono is a complete and viable solution for non-windows operating systems. If you don't think it is, I seriously doubt you have ever used it.
Despite the comment threads already going on, there are a few reasons why C/C++ isn't being used:
1) To prove it's possible to write a CLR-based OS
2) The fact that an OS based around a memory-safe language and runtime is inherently more safe. You eliminate the majority of normal bug openings (buffer overflows especially). And without needing to use segments and separate CPU privilege levels, you don't have to do context switches.
3) Most interesting to me is that by distributing code in a bytecode form, you get platform independence without having to distribute source. Device manufacturers can write a driver, distribute in bytecode, and not have to compile for every architecture, kernel version, etc. Nor do they have to distribute source, which somewhat protects trade secret interests (I know, bytecode can be easily reverse-engineered. But it's a "see no evil" effort, in my opinion).
Hope that made vague sense.
Makes perfect sense. Between Cosmos, SharpOS ( http://www.sharpos.org/ ), and JNode ( http://www.jnode.org/ ), I think we all have a bright future ahead of us.
We won't even have to make the mistakes of eternal backwards compatibility that Windows makes, because we can efficiently emulate other OS' ABIs using OOP abstractions and opcode recompiling.
All hail open-source. Hallowed be the architects.
First, C# isn't a "Microsoft-only framework/language". It's a public ECMA standard. See mono-project.com.
Second, C# has a lot of draws over C/C++: lower complexity, platform-independence, garbage collection (no more leaked pointer references), consistent advanced language features (ie. threading, exceptions, events, timing, delegates, templates, etc), rapid prototyping, JIT compilation (and support for on-the-fly compilation of classes).
Third, I don't think it's a question of "Why use C# over C/C++?" but, rather, "Why use C# over Java?" Computer languages are just abstractions. Java and C# can be reduced to native code just as readily as C/C++, and they contain all of the necessary constructs to write an operating system. Java and C# are both up to the task. I'm not sure why the project chose C#; except, of course, that tool support for C# is very good with Visual Studio (I don't care for Eclipse--just my personal preference).
I totally disagree. Not sure how you formed this conclusion, but you're wrong. Mono is an excellent open source implementation of C#.







Member since:
2007-01-24
What is the problem with C++ or C and why use a Microsoft-only framework/language (yes, Mono is not a complete and viable alternative for non-windows operating systems) ?