CSUMB

CSUMB 334 - Week 8

Author

Date Published

CSUMB logo 2

Write a 1 - 2 paragraph journal post, of at least 250 words, summarizing what your biggest takeaways from CST334 were, including any major challenges or topics you found particularly interesting.


My biggest takeaways were really grasping exactly how much stuff the OS is doing behind the scenes when I am running programs. Before this I had a rough/fuzzy understanding of how a computer works. I understood that a computer had temporary "fast" memory (ram), it had slow "permanent" memory (hard disk), it had a CPU that did the calculations, sometimes computers had GPUs that did a special niche set of calculations. But, beyond that I had no idea how different programs didn't collide when sharing resources.

Now I have a much more clear understanding of how the OS diversifies available resources among running programs. I understand how computer (CPU) time is shared via scheduler among running processes. I understand how the available memory is allocated to given programs and how potentially more memory can be allocated. And most recently, I understand how permanent storage is allocated for quicker access.

That being said, I am not sure I will be able to recollect all the math necessary to reverse engineer this stuff after this class. But, I think that's okay, if I ever need it I know what I need to look for and how to look for it. I also hope to be programming at a much higher level than OS C.


It's actually funny I had an issue at work this week with a javascript library that depended on a C library. But, I was running this javascript library on different Operating Systems and I had to deal with getting it to run on `musl` rather than the standard `glibc`. Without this class that task would have been impossible so it's already paying dividends.

Comments

michael sorensen
michael sorensen

I wonder if these comments still work

michael sorensen
michael sorensen

nice

Join the conversation! Login to reply to comments