speewave wrote:
i am a verry impatient programmer!!!!
i guess we noticed that already
Let me try to open your eyes on the hidden part of writing an OS...
You say you want e.g. an office suite. fine. You'll indeed need a graphic library for that, but let's see what else.
You certainly want the ability to copy/paste data accross applications, right? here too, that requires communication between running programs using some of the OS API.
Oh, and you want to save files, for sure. Here again, that involves OS services to translate "my_docs/idea.txt" into "somewhere to place it on the hard disk". and again, the OS and its drivers will have to make sense of the data read/write requests of your apps, find appropriate locations on the disk (based on some structure informations like the FAT), and put "magic" values into hardware registers so that the disk drive know it should start spinning, move heads at a given location and start reading data that you'll read back to interprete the "my_docs/" directory and see whether the "idea.txt" file already exists or not ...
And just if it wasn't too complicated already, then comes hardware heterogeneity. Your "hard disk" could have been an USB key with its own suite of rules and protocols, or a SCSI or SATA device ...
Being an OS developer, that is reading a lot to figure out how all those things in your PC work, and how you can use them to provide services to applications.
Now, maybe you're not interested in writing the
kernel of your new OS and that you'd rather run on an existing kernel (linux, QNX, L4, the mobius, reactos or whichever you find suiting your needs).