Cute Aaron ... we can all appreciate some good tongue-in-cheek humor. <g>

~~Bonnie


>Hi all,
>
>I find this all very sad.
>
>IMHO a commercial framework is nothing more than another tool in our development toolbox. It sits alongside other tools such as VFP, C#, numerous development books / help docs, SDKs, ODBC, etc. etc. (and even the .NET framework itself).
>
>If the question here is whether or not we "real" programmers use commercial frameworks then I would also assume that we "real" programmers would also:-
>
>1. Write our own applications in pure machine code without the use of an assembler (after all an assembler is a tool written by someone else and we don't like that<g>). In addition, don't call any functions in the operating system or the BIOS as we don't like relying on other people's code and would prefer to write both the operation system and BIOS ourselves<g>.
>
>2. Don't use ODBC / OLE DB drivers as they have been written by someone else and they add an extra layer which imposes a overhead. Much better to write own own data access code - in fact let's not stop there, let's write our own version of SQL Server while we are at it <vbg>.
>
>3. Don't use any of the .NET framework libraries for the same reasons. Also, don't use any "commercial" components (such as Infragistics) as we "real" programmers prefer to write our own. Don't even use the standard .NET controls for the same reason. In fact, let's forget about .NET as we will have already written our own operating system by now and we can start work on our own version of .NET<g>.
>
>4. Don't read any development books because we don't intend to use anything else - we will write our own version of everything<g>.
>
>5. Invent our own processor as it is outrageous that Intel should think that we would ever want to use their instruction set<vbg>. As for IBM - where's my hammer and nails ?
>
>I could go on...
>
>I would have thought it would be difficult for anyone using the .NET framework, a development language (such as C#, VB, etc.) and possibly several other third party "components", to suggest that commercial frameworks are not for "real" programmers. What is the difference between using raw DataSets as provided by MS in the .NET framework and the extended DataSets in a commercial framework ? How can one be right and the other wrong ?
>
>Of course, everyone is entitled to their opinions but it starts to become dangerous when the opinions can be read as "we are better than you because we do it a different and better way and you are not clever enough to do it as well."
>
>I will close by saying that I a "real" programmer and I insist on doing everything myself because I am really clever and I want you all to know that<g>. I am using a keyboard to type this message that I personally designed and built myself (must remember to include a DEL button in my next version<g>) and I have sent this message via my own version of the Universal Thread that I programmed myself<g>. I have to sign off now as my own personally designed and built computer come shower room doesn't run off electricity and my legs are getting sore on my "bicycle generator" <vbg>.
>
>I hope I haven't upset anyone as I think there are more important things in life and I am simply trying to make that point<g>.
>
>By the way, don't reply to this message as my own version of the Universal Thread only sends messages - I haven't got around to adding the reply code yet<g>.
>
>Regards,
>
>Aaron