5 ms·

How much of "writing an OS from scratch" do you think you could've done within 1 year using all the tutorials available on the Internet? Please provide links

by mythz 7y ago

How much of "writing an OS from scratch" do you think you could've done within 1 year using all the tutorials available on the Internet? Please provide links to some of these magic tutorials that makes developing an OS from scratch as easy as creating an iOS App. Like which part of "creating an OS" would you have tackled first, using which tutorial and how much time do you think it would take you?

yjftsjthsd-h 7y ago
So... To be clear, I agree that the task is monumental, and on this scale no tutorial will help (much like there is no "how to write a complete web browser" tutorial). However. > Please provide links to some of these magic tutorials that makes developing an OS from scratch as easy as creating an iOS App. Like which part of "creating an OS" would you have tackled first, using which tutorial and how much time do you think it would take you? https://wiki.osdev.org/Tutorials https://wiki.osdev.org/Tutorials > follow in order, take a few months, and you absolutely can write an OS.
seabird 7y ago
I feel like I could pretty comfortably write sizeable portions of an OS if I invested as much time as the author of Serenity did. I'm not trying to talk up my own capability or downplay the Serenity author's achievement, I just think a lot of people don't realize that low-level programming isn't really harder, it's just different.
- FpUser 7y ago
  Second that. In my life I did everything from programming in pure machine codes (big device control, data processing an presentation system) to modern firmware to desktop apps with multimedia and high performance graphics to back end enterprise grade middleware like business process servers, publish subscribe, NoSql, etc. etc, To me they were not that different in difficulty. Just different scope techniques and tooling. For example by concepts message passing part in that machine code system and large publish subscribe looked very close.
- akling 7y ago
  You totally could! The individual tasks are not inherently difficult or challenging. It's something I'm frequently trying to explain to people, and a big part of why I started showing my programming sessions on YouTube: to demystify "OS development" as a concept. The actual challenge is staying consistent and persistent, day in and day out, for a long period of time :)

by mythz 7y ago

yjftsjthsd-h 7y ago

So... To be clear, I agree that the task is monumental, and on this scale no tutorial will help (much like there is no "how to write a complete web browser" tutorial). However. > Please provide links to some of these magic tutorials that makes developing an OS from scratch as easy as creating an iOS App. Like which part of "creating an OS" would you have tackled first, using which tutorial and how much time do you think it would take you? https://wiki.osdev.org/Tutorials https://wiki.osdev.org/Tutorials > follow in order, take a few months, and you absolutely can write an OS.

seabird 7y ago

I feel like I could pretty comfortably write sizeable portions of an OS if I invested as much time as the author of Serenity did. I'm not trying to talk up my own capability or downplay the Serenity author's achievement, I just think a lot of people don't realize that low-level programming isn't really harder, it's just different.

FpUser 7y ago
Second that. In my life I did everything from programming in pure machine codes (big device control, data processing an presentation system) to modern firmware to desktop apps with multimedia and high performance graphics to back end enterprise grade middleware like business process servers, publish subscribe, NoSql, etc. etc, To me they were not that different in difficulty. Just different scope techniques and tooling. For example by concepts message passing part in that machine code system and large publish subscribe looked very close.
akling 7y ago
You totally could! The individual tasks are not inherently difficult or challenging. It's something I'm frequently trying to explain to people, and a big part of why I started showing my programming sessions on YouTube: to demystify "OS development" as a concept. The actual challenge is staying consistent and persistent, day in and day out, for a long period of time :)