SharpOS in the Stream of C# Kernels
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."
E-mail Print r 1   29 Comment(s) http://osne.ws/ey5
Thread beginning with comment 301989
To view parent comment, click here.
To read all comments associated with this story, please click here.
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

Yamin Member since:
2006-01-10

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

As I've developed in the software engineering world, I've come to have an infinite amount of sympathy for hiring managers. It's virtually impossible to tell who is a good programmer. Much less what is 'experience'?

I'm worked at places with dead weight programmers who quite frankly are idiots. I'm sure their resume looks great with 10 years experience with Nortel (speaking as a Canadian...seen too many of these) or some other company.

I've met guys with 10 years c++ experience who still don't really understand how to program properly for it. On the other hand, a good engineer DOES investigate and make sure they understand the language before going into the code. For example, I used to be a purely c/c++ guy, but was eventually assigned to a c# project. I read up on it, made sure I understood it. Suddenly I start seeing fundamental flaws in how the project was currently written (by people with 3-4 years c# experience.

Also, c/C++ are not the same thing. Hiring someone with C experience to do C++ is a recipe for disaster. Just last night I spent 3 hours debugging a problem because someone forget to implement a c++ copy constructor for a class when using the STL. None of those terms mean jack for a C programmer.

So in conclusion. Hiring a programmer/software engineer is insane. There's no magic in it. I really think everyone should make use of that 3 month probation rule that comes with most contracts. If the person is not as capable as you thought, let me go in the first 3 months. If the worker doesn't quite like the workplace...they should feel no guilt leaving the company.

Reply Parent Score: 2

Read more of this thread... >