But in my line of work, who cares if meet some ideal of "expert"? I need to develop solutions, not impress my users with my OS knowledge. I can get down and dirty with the best of them, but I prefer to have the development tool/environment do it for me. Anyways the .Net Framework is basically just another OS you program for, the same way you program for the JVM. You need to understand it to develop quality applications for it.
Jamie
I agree that using a tool to make your life easier and your time to market faster is a good idea. However, I don't think you can compare a framework that wraps an operating system to an operating system (i.e CF .NET to PalmOS 6).
It has been my experience, and I imagine yours too, that when a developer gets stumped on a problem (in any framework) and they don't understand the inner workings of the OS (or whatever is being wrapped), they struggle to come up with an acceptable solution. Situations like this lead to hacks and bugs and usually a break down in design.
My original point is this. PalmOS, at an operating system level, is easier to understand than Windows (whether it be PPC or XP). Palm did a good job of keeping simple. Kudos to MS for their .NET framework. It makes things easier, but, it is not an excuse to not understand how the OS works. Trust me, I love the fact that I can bang out two million lines of code by writing 6 function calls in VB.NET!
Brad
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
