I'm not saying that native compiled (C, C++) code is bad. They both have their purpose.
I wouldn't imagine writting a device driver purely in Managed code. Even though it may be possible (I don't know.)
Now, lets take an example. You have to write a custom Windows.Forms based application that keeps track of After school activities/attendance and billing. Don't tell me you could write it faster in Native C/C++ than you could in C#. With this example, I don't want to have to worry about writing an XML Serializer, or writing the piddly code that makes sure things resize appropriately when you resize the form, or any of the other tedious tasks that just waste time and prevent me from adding more quality features to the application. If your primary job is to write applications that in simplest terms, read and write data to a database, you don't want to or should need to worry about writing your own XML Serlializer.
And you can do low level stuff (write un-safe code). You have access to all the Windows API's. And you could write your own XML Serializer if you wanted. You still have all that power, but you also have the choice to use pre-built components that you don't have to worry about working and they save you time.
Beer28 wrote:It's just that I'm at a point now where I'm sick of all that abstract layer technology. It's better to build on C libraries.
That's kind of funny, since I am sick of having to write all these things from scratch. The .NET Framework allows me to write custom applications faster. Wouldn't you like to charge the same amount for developing an app with .NET as you would with native C/C++, but take less time developing it because you used .NET???