the kernal process was a cache memory for all processes and cores … it was a line of script that the user does ... stored as a ROM memory, or rather "cache memory"
The processors and cores uses that script to store your current session ... save the software file, the file was moved into your storage disk.
Totally incorrect.
The kernel (k - e - r - n -
E - l) is the core of your operating system. The programs that are running on your computer are pretty stupid, i.e. the
machine code is just a sequence of instructions related to the task at hand and nothing more.
Every time a system-wide resource (like a
file or a network
socket) is needed, the process doesn't take care of it directly, i.e. the developer doesn't have to code against your bare hardware, he uses
system calls.
"Hey kernel, gimme four megabytes of memory, I need it to do stuff, I'll return it, I swear."
"Hey kernel, I need to do some networking, gimme a socket I can use."
"Hey kernel, there's this file called "Research.mp4" in a folder called "totally_not_p0rn", and I would like to open it read-only, gimme the file descriptor"
"Hey kernel, I have nothing to do right now, so I'm going to sleep for a while. Wake me up in one second, okay?"
"Hey kernel, what time is it?"
These are all examples of system calls. An unprivileged process can't do any of these things directly, as that would be incredibly insecure, so the routines needed to open a file or get free memory are coded in the kernel and only accessed via these standardized system calls.
The second most important thing the kernel does is
multitasking.
At every given moment, there seem to be dozens or hundreds of process "running" on your computer. The truth is they are not running, they're just switching extremely fast on your limited number of CPU cores. This switching can be voluntary (that's called
cooperative multitasking), which implies that a programmer has to specify points in the code where the processing pauses gracefully and is replaced by another task. Now this is a dangerous thing to do as a rogue program is able to totally block the CPU (i.e. never yield to another task) and force you to restart the system.
In macOS (and Windows and most Linux versions), this switching is involuntary and managed by the kernel (that's called
preemptive multitasking). The kernel acts like the guy with a stopwatch that lets a process (a thread, to be precise) on the CPU and then after some time (tiny fractions of a second) kicks it out no matter what.
So these are the two most important things the kernel takes care of in your computer, so developers don't have to. Of course there are many more and if you're interested, then
Wikipedia is your friend.