[flagged]
Facts. What I wonder is if everyone else wants to believe or really just doesn't care. For some reason, I really hate being lied to.
I'm 17 and wrote this guide on how CPUs run programs
241–250 of 327 posts
Re: I'm 17 and wrote this guide on how CPUs run programs
#242Kid, first of all great job! Second of all I am jealous you understand this as such a young age. I was pounding 40 ounces of Old English in the hood at 17, but should have doing something like this. Granted, the internet was just a baby when I was 17.
Re: I'm 17 and wrote this guide on how CPUs run programs
#243Great effort, but really still needs a bunch of work. In some places the sentences just don't make sense. I think in terms of CPU, a good starting point is the Von Neumann architecture which most computers are designed around.
The current description of CPUs mix things up with OS concepts. You may want to look into things like memory management units ( MMU ) that builds on the basic Von Neumann architecture to provide "virtual memory" such that an OS can use it to provide process isolation that OS's can use. Also the more capable CPUs have what are often called "modes" (protected mode in x86, ARM have a similar thing) to isolate running programs from each other and be able to create rings for things like kernels and device drivers.
Re: I'm 17 and wrote this guide on how CPUs run programs
#244This is legit, nice work! I'm going to link this to some friends
Re: I'm 17 and wrote this guide on how CPUs run programs
#245OP, don't excuse your work by prefixing it with your age. Your write-up is better than most people will ever do. Nice work!
Very unlikely anyone would care about this ChatGPT-level summary of how a CPU works if the author didn't mention they were 17.
Re: I'm 17 and wrote this guide on how CPUs run programs
#246When I was 11 I coded in assembly and machine language, what do I win?
Re: I'm 17 and wrote this guide on how CPUs run programs
#247This is on my reading list. This little bit sold me on it in the past: > The bottom of every page is padded so readers can maintain a consistent eyeline. Such a tiny and, in hindsight, obvious detail. It's surprisingly pleasant. When I noticed that, I knew I had a passion project in front of me.
There are quite a few very nice UI touches. I think the bit about the author (authors?) being 17 is relevant because it seems like they put a lot of thought about how to represent a book on the web and came up with some new conventions, just like you'd expect from a new generation. The chapter navigation widget at the top for example, where the previous and next chapters are slightly opaque. Haven't seen that before.
That is indeed a nice touch. I've seen that before in presentations generated usingn LaTeX Beamer templates.
Re: I'm 17 and wrote this guide on how CPUs run programs
#248I thought it’d be lower level as it’s still very abstract and more of an operating systems guide than a guide on how CPUs physically run programs. Like how a string of current representing 1s and 0s allows the CPU to do certain things, etc.
But well organized none the less!
Re: I'm 17 and wrote this guide on how CPUs run programs
#249Re: I'm 17 and wrote this guide on how CPUs run programs
#250Earlier quoted context omitted.
I can't resist pointing out that LWN ( https://lwn.net/ ) has been dedicated, for many years, to the production of operating-system information that is not terrible. Have a look, and perhaps consider joining us :)
LWN is one of my favorite websites. I learned more from LWN articles (probably mostly yours lol) than most other resources on the internet when researching for my article. I actually quoted you from 19 years ago! https://cpu.land/epilogue#bonus-tidbits
Same.