Linked by Thom Holwerda on Fri 22nd Feb 2008 09:16 UTC, submitted by obsethryl
.NET (dotGNU too) "Previously, we have presented one of the two opensource licensed projects related to creating a C# kernel. Now it's the time to complete the set by rightfully presenting SharpOS, an effort to build a GPL version 3 + runtime exception licensed system, around a C# kernel of their own design. It is my pleasure and priviledge to host a set of questions and answers from four active developers of SharpOS, that is William Lahti, Bruce Markham, Mircea - Cristian Racasan and Sander van Rossen in order to get some insight into what they are doing with SharpOS, their goals, their different design and inspiration."
Thread beginning with comment 301977
To view parent comment, click here.
To read all comments associated with this story, please click here.
ahmetaa
Member since:
2005-07-06

Just like Jnode with Java,
Basically safety is the answer. no buffer overflows or easy memory leaks. Also development speed is a big bonus.

Reply Parent Score: 5

erdizz Member since:
2006-06-07

To my understanding, buffer overflows and memory leaks are only a fraction of the sources of instability in modern kernels, while synchronization issues in highly parallel asynchronous environment and general complexity problems are probably more significant and harder to solve. Managed languages don't help with the latter, so it's not a silver bullet.

Reply Parent Score: 5

l3v1 Member since:
2005-07-06

safety is the answer. no buffer overflows or easy memory leaks


Well, actually all you do is delegate the safety checks to the developers of the language/compiler/whatever. In the long run all I see emerging from this is something I don't really like, coders who say are experienced and perform horribly when needed to code in c++ and the likes. And disregard c/c++/vc/etc. all you want, it's still mighty important. Don't get this wrong, I personally don't have anything against c# (although winforms is a no-go for me), on my better days I tend even to like it somewhat ;)

Reply Parent Score: 3

dagw Member since:
2005-07-06

In the long run all I see emerging from this is something I don't really like, coders who say are experienced and perform horribly when needed to code in c++ and the likes.


This is simply solved by hireing people with the skills you actually need. If you need a C++ programmer hire someone with C and/or C++ experience. Expecting someone who knows how to 'program' to perform equally well at all programming tasks and in all languages is silly.

If I need someone to write numerical analysis software in C I wouldn't hire someone who's an expert at writing web apps in perl.

Reply Parent Score: 3