Talk:Rolling Your Own Bootloader
Are we keeping this page and fixing it up or are we going to move its contents to somewhere else? It would be nice to know before I go and fix it up. Thanks. --Frank 09:46, 3 July 2007 (CDT)
- I already rewrote parts of the article a while before this version was moved in with the fast merge. The main difference is that the other article is more theoretical but lacks some information that was present. I think we should decide here which way to go:
- fix this article and remove Bootloader
- copy the remaining information to Bootloader and remove this article
- move all remaining theory to bootloader and keep all practical info here in a separate article.
- My choice would be either option 2 or 3, largely depending on wether keeping two articles is useful. One could add some extra information to the practical aspects, at which point #3 becomes the better one. At the very least we should compare the articles and see what information is missing from either one. - Combuster 06:25, 5 July 2007 (CDT)
- I think that I like 3 better. Moving of this information would just clutter up the theory article. This one is more of a how-to anyways. --Frank 15:36, 5 July 2007 (CDT)
Broken link in 'How do I actually load bytes' section
The broken link is the 'see OSRC for more info'. I've been perusing the root site but I never saw the original link, so I'm not sure exactly what I'm looking for, I just know there is no 'os' section anymore. I'll keep looking, but I wanted to make a note to see if anyone had more luck than me.
-- Jflopezfernandez 12:35, 12 August 2019 (CDT)
Its very biased
Rolling your own bootloader is very biased and has a very negative tone. That's what I got from it. The neg tone set from the start from the author made it hard to concentrate on the actual page written. There are a lot of people who prefer to learn and write their own stuff, it makes them feel like they accomplished something, even its something little. There are a lot of people who don't care to use tools. It was said that if a bootloader source code was presented then someone would be using that premade bootloader instead of trying to make one and that is the not case at all.
There are quite a few people who actually study the source code to understand it even if they never use the product. I mean how many times have you found your self re-reading something until you finally understood it? Tracing labels and their connections. That's not possible if nothing is presented. How else are you to ever become one of the old greats, if you never study, different sources of code? Maybe someone would like to compare styles and learn new techniques from what they read. How else are you suppose to write things from scratch and learn the more difficult things if only tools are being shoved down your throat. All of these things contribute to making better coders.
At what point does the art become lost?? Idk. I like os dev but starting to hate all the biased pages with limited and narrow views. What is the point of even writing a page if you are not going to properly cover the topic? If you have the knowledge, on a knowledge giving/providing site, but are refusing to share the knowledge. That makes no sense. Is this not a site to come and learn how to code the things you want to learn to code? I almost felt the reason the author didn't provide the bootloader, was because he himself has become too reliant on tools, that he was unable to provide the bootloader from lack of knowledge. Not trying to start a fight, not trying to be rude, or anything like that. Its just what I personally took from the page. I am not completely against tools either, because I use some myself, that I find help the workflow. I am merely writing my view point on this page because it has irked me every time I have read it. This was/is an introductory page, is this really the tone, we want to set for new visitors when they read from the beginning?