What Order Should I Make Things In?: Difference between revisions

← Older edit

What Order Should I Make Things In? (view source)

Revision as of 19:04, 9 July 2023

676 bytes added , 11 months ago

no edit summary

[unchecked revision]

VisualWikitext

Anonymous user

osdev>Khaledhammouda

Revision as of 09:10, 15 October 2016 (view source) Glauxosdever (talk \| contribs) (Add Mister Perfect) ← Older edit		Latest revision as of 19:04, 9 July 2023 (view source) osdev>Khaledhammouda No edit summary
(23 intermediate revisions by 4 users not shown)
Line 14: == Style Extremes == OSDev seems to have "archetypes" among the ~~OSDevvers~~OSDevers (and the OS they develop). Of course, the idea that most people have of a "complete" kernel includes most (if not all) of the items listed below. === Lino Commando === Line 22: === Nick Stacky === {{main\|Nick Stacky}} His test-machine has no keyboard and no screen (no one needs that). All he needs is NICs (Network Interface Cards) ... plenty of NICs ... and an ~~ethernet~~Ethernet cable to see if his kernel responds to pings and routes packets correctly. His kernel has powerful multithreading and a complete TCP/IP stack, of course. === James T. Klik === Line 47: {{main\|Mister Perfect}} Mister Perfect wants to write a perfect operating system, as he looks at all the flaws current operating systems have. He researches many design and implementation possibilities in order to decide what is better. He starts over multiple times in order to assure quality and perfectness. === Andy Microbaum === {{main\|Andy Microbaum}} Andy is a fan of small kernels who put much stuff done in a monolithic kernel into userspace. === Dizz Tracked === {{main\|Dizz Tracked}} Dizz gets distracted by unneccessary side projects. === Mono Lizzy === {{main\|Mono Lizzy}} Lizzy likes to put everything into one big kernel. === Ideas for new Archetypes === * '''Edward Scissorhands''' - Sounds like something designed on paper to do everything but completely broken in practice, I see architecture astronauts rather doing vaporware (e.g. you'd never get to see the Scissorhanded implementation the architecture would require) * '''Real Man''' - Writes an entire operating system in ~~assembly~~Assembly, preferably in real mode. Abhors [http://en.wikipedia.org/wiki/Real_Men_Don't_Eat_Quiche Quiche Eaters] and [http://en.wikipedia.org/wiki/Real_Programmers_Don%27t_Use_Pascal Pascal]. * '''Andy Microbaum''' - Microkernel people. * '''Vizier Studio''' - Visual Studio people. * '''Barry Pi''' - ARM people. * '''Racing Carl''' - Does all in protected mode Assembler and rewrites the latest 3D library and tries to squeeze the last bit of speed out of the code. === Archetypes to avoid === * '''[[Cowboy Coder]]''' - Someone who eagerly jumps into coding without any plan. * '''[[Dae Dreamer]]'''- Someone who spends all their time day dreaming and reading about operating systems, but hasn't yet started one. * '''[[Duct von Tape]]''' - Someone that reuses a lot of code and combines it into a horrible frankenstein of a project. Or perhaps [[:Category:Lovecraftian\|lovecraftian]]? * '''[[~~Bossy~~Sir ~~Boots~~Dunning-Kruger]]''' - Someone ~~that wants other people to fix their~~overestimating ~~bootloader~~his/her ~~for~~skills ~~them~~dramatically. [[Category:OS Development]] [[Category:FAQ]]