Kyren223/resources
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Changed wording to be less rude

Browse Source
This commit is contained in:
Kyren223
2025-09-26 00:33:01 +03:00
parent bb25494895
commit 65fa70530e
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -12,7 +12,7 @@ I link/refer to [Krypton](https://git.kyren.codes/kyren223/krypton) a few times,
am working on currently, it's in closed beta (such a JBlow move, IK lol),
If you want access to the repo, just ask me on discord or email me at `<contact@kyren.codes>`.
*Also gitea doesn't support footnotes apparently, when u see `[^N]`, go to the bottom to see the footnote.*
_Also gitea doesn't support footnotes apparently, when u see `[^N]`, go to the bottom to see the footnote._
## Recommended order
@@ -74,7 +74,8 @@ I'd recommend either skipping it, or rewatching it multiple times, until you ful
### How to ACTUALLY manage memory (it's easy!)
First, realize you _do not_ know how to _actually_ manager memory, so throw away all the misconceptions u have been taught.
First, you have probably been taught the malloc/RAII way of managing memory, which is needlessly hard, throw that stuff away.
Here is how to actually manage memory in a simple and straightforward way:
[How memory works by Kyren223 (me)](https://kyren.codes/blogs/how-computer-memory-actually-works/) - Goes over how your program interacts
with memory nowadays, knowing about virtual memory and virtual address space would be crucial to
@@ -108,7 +109,6 @@ But tldr; handmade hero, all of it, then u should be able to learn on your own.
Also for math, the [BSC 2025 talk by Ginger Bill](https://www.youtube.com/watch?v=YNtoDGS4uak), and Freya Holmer's [Math for Gamedev](https://www.youtube.com/watch?v=MOYiVLEnhrw&list=PLImQaTpSAdsD88wprTConznD1OY1EfK_V) series.
### Compiler and Language design
TODO: this took me very long to make, will add this later (remind me if I forgot!)
@@ -137,4 +137,4 @@ and probably some more that I forgot.
[^1] Unless u write your own OS, but even then, you'd be interfacing with hardware. and I assume you are not going to manufacture your own CPU.
[^2] Certain CPUs use 52-bit or 56-bit, because of some super computers hitting the 256TB limit (bruh)
[^3] Some arm CPUs have TBI (top bits ignore), to allow storing metadata in the top 8 bits of a pointer
[^3] Some arm CPUs have TBI (top bits ignore), to allow storing metadata in the top 8 bits of a pointer