21–28 of 28 posts
He also created a remake of this in C called "mos". Kind of irks me that he does "if(var == true)" instead of "if(var)" in certain spots though.
He's 15, I think it's okay to cut him some slack
Even though I haven't tested it, not bad coming from a "15-year-old computer hobbyist". Congrats!
A 15 year old Egyptian kid made a new OS in asm who wants to study medicine. Sounds like he needs to go to SV, I think he'd fit right in.
When I was 15, I'm not interested in learning computer programming yet. Mostly just played games, like Duke Nukem 3D or :/
Curiosly, it was a book about computer virus programming (obviously in assembly) which hooked me into coding :D
Why not 64 bits?
If you want to write an OS with a GUI on modern x86 hardware from scratch, there is an insane amount of stuff you have to do to support a generic keyboard, mouse, and display before you can do any work on your OS proper.
He's not alone in this, but the way; another OS author wrote "it probably never will support anything other than AT-harddisks, as that’s all I have :-(."
Earlier quoted context omitted.
I donno if this is a serious question or not, but x86-64 is very much an extension of regular 32-bit x86, just more complicated. For something like this there's little reason to attempt 64-bit when 32-bit is much easier and will essentially result in learning the same concepts.
There are real benefits to using x86-64 over x86, namely, x86 is starved of general purpose registers. There are many more registers available on x86-64.
He also created a remake of this in C called "mos". Kind of irks me that he does "if(var == true)" instead of "if(var)" in certain spots though.
He also created a remake of this in C called "mos". Kind of irks me that he does "if(var == true)" instead of "if(var)" in certain spots though.