i got inspiration from this #link("https://os.phil-opp.com")[blog]

== notes
will use as much crates as possible
- has to be up to standards
- has high quality

== booatloader selection
i could just use qemu skipping to kernel but i wanted to explore about bootloaders too since im making a os, but i dont wanna spend all my time just doing repetitive stuff and dealing with legacy stuff
two realistic options only:
#link("https://crates.io/crates/bootloader_api")[bootloader_api] which is what the aforementioned blog uses
rejected because:
- don't wanna deal with manually setting up SMP
- hands me a poor memory base my mmu off of
- more niche(thereforee less mature/popular and therefore getting less support) and only gain traction due to the aforementioned blog post
  - due to that it's tightly coupled with it
#link("https://crates.io/crates/limine")[limine]
- cons: no documentation
=== changed to bootloader api as it's more idiomatic and appearently has better documentation

== spinlock
thanks ("https://www.reddit.com/r/cpp/comments/1w6us70/optimizing_a_spinlock/")[this reddit post] and subsequently ("https://david.alvarezrosa.com/posts/optimizing-a-spin-lock/")[this blog] making me realize this was even a possibility

== mm
- using Higher Half Direct Map provided by bootloader api crate
- custom new type for virtual and physical memory for type safety

== panic & backtrace
thanks ("https://eli.thegreenplace.net/2011/02/07/how-debuggers-work-part-3-debugging-information")[Eli] teaching basic concepts and ("https://wiki.osdev.org/Stack_Trace")[osdev] for a practical example

== exceptions
used x86_64 crate however still read ("https://os.phil-opp.com/edition-1/extra/naked-exceptions/")[this blog] to understand