Fabrication also depends on what is designed, no? There is a coupling between the two?

Not in most cases. Apple, AMD, and most other chip makers lack a fab. The design what the fabs can make, but they don't have much input into the fabs. Someone makes a fab, and you make something it can made.

Of course things are never that neat. I have no doubt the large players have input into the fabs - we have no idea what. However the two teams are still different companies, when the fab and chip design are the same company there is the possibility of more cooperation (or less - we don't know. In the best case for both there is more when it is all internal, but we don't know if this is the best case)

I am considering more dynamic "tutors", since this rudimentary version got so much attention! :)

What do you have in mind when you say "step through" the code? Like follow your scrolling of the source code?

Something as simple as an LLM prompt that explains what the file does would go a long way I think.

Can you please elaborate what exactly is the problem with the first sentence?

"The kernel isn't a process—it's the system. It serves user processes, reacts to context, and enforces separation and control."

This is actually based on "The Kernel in The Mind" by Moon Hee Lee. You are welcome to provide feedback.

> This is actually based on "The Kernel in The Mind" by Moon Hee Lee.

This looks like a really interesting resource. Can anybody here vouch for its accuracy or usefulness? I can't find a ton about it online. The fact that it's only published as a series of LinkedIn posts, or a PDF attached to a LinkedIn post, does not fill me with confidence - but I guess we can't expect kernel devs to know how to create websites?

Is it or is it not AI generated? That's all I said, and you didn't deny it.

Focus! Whether it's AI generated or not is a form of ad hominem. Attack the content, not how it came to be.

> This isn’t a guide to writing kernel code. It’s an effort to understand how the Linux kernel thinks.

> not of function calls, but of how the kernel responds

> The kernel is not a process but the very foundation

> The Linux kernel is not just a set of subsystems—it is a layered system that enforces structure at runtime

> This flexibility does not come from runtime detection or dynamic reconfiguration. It comes from structure.

> Identity is not discovered at runtime. It is defined before execution begins.

> The kernel doesn't view memory as a simple map, but as a responsibility

> Memory Is Not a Place. It’s a System.

> Memory safety relies on disciplined handoffs, not centralized control or type enforcement.

> The Linux kernel goes beyond executing code; it enforces strict control

> Kernel execution is not linear code—it’s structured control

This legitimately hurts to read. I think I'm going to have an aneurysm if I continue.

Do you have any constructive feedback on how I can fix it?

Have a human write it instead of ChatGPT.

I cannot reproduce. Would you mind sharing a bit more? The certificate is handled by Cloudflare Pages.

My bad, the network I was connected to didn't like the certificate for some reason. Cool project!

Thanks for the observation about mobile responsiveness, I will improve it!

Thanks for sharing OP! It seems quite some people liked it, so I'll be listening to feedback and see what to do next. :)

Hey! Thank you for catching this issue and reminding me of the super naive implementation I went with. I will improve this! :)

It’s often better to overlay caching and other tricks on top of naive implementations than making the implementation more complicated.

* until you get caching layers more complicated than the more complicated implementations :) Imo strong implementations can be much simpler and more predictable than caching.

The Elixir cross referencer does not have any special features to help you learn