Updare writeup and gitignore

.gitignore

@@ -5,4 +5,6 @@ bin/*
 
 .clangd
 
-include/binding/ruby_compiled.h
+include/binding/ruby_compiled.h
+
+p.vim

writeup/analysis.md

@@ -1,5 +1,3 @@
-# Outline
-
 # Analysis
 
 ## What is a game engine?
@@ -262,8 +260,27 @@ extra:
 
 - super simple neural network system (with training and runtime phases) (if i have enough time)
 
-## Embedded scripting language choice.
+## Hardware
 
+get steam data on hardware usage around the world explain my setup testing on a msi core 7 / 5060 and iGPU and ideapad
+for software make sure it works on linux and make it theoretically work on other os but do not test or check for it
+
+## Libraries / dependencies
+
+### Rendering
+
+#### why use a rendering lib
+
+
+
+#### why use SDL3 / what options there are
+#### how i will use sdl3 exactly
+
+### Embedded Scripting
+
+#### why do i need an embedded scripting system (use godot and how it does as reference)
+#### What options do i have.
+#### Why use Mruby
 Why ruby is great for development for the runtime of this engine:
 
 - Dynamic typing. it has almost no type declarations on variables, and duck typing means any object with particular behaviour can be treated the same.
@@ -285,10 +302,12 @@ The engine could compile the developers scripts into mruby bytecode when buildin
 
 ^ Mruby.org. (2026). mruby - Lightweight Ruby. [online] Available at: https://mruby.org/ [Accessed 13 May 2026].
 ^ Ruby (2019). Ruby Programming Language. [online] Ruby-lang.org. Available at: https://www.ruby-lang.org/en/ [Accessed 13 May 2026].
+#### how i plan on using it along with all precompiling/packing plans i have.
 
-##
 
-- then a draft one of the requirements with justification of each based on the previous sections
+## Requirements
+
+- then a draft of the requirements with justification of each based on the previous sections, along with information on how id use a seperate packer system
 
 Requirements v1:
 
@@ -315,10 +334,4 @@ Requirements v1:
 
 ##
 
-- then any limitations / problems that can arise with certain choices in that list and how i might tackle them or ignore them
+- then any limitations / problems that can arise with the choices in this list and how i might tackle them or ignore them
-
-- then specifics of what ill need to actually make this, like the libaries, languages & hardware ill use with reasons of why, can have a big section on stuff like explaining why i chose sdl3 for rendering, or mruby (mostly because of mruby precompiling and how i can prepack the engine into a single binary)
-
-- and finally a rigid list of requirements of things it should be doing by the end with 2 priority levels and this time just the list and not any justifications this time
-
-# REDO section on sdl3 and mruby again