F
F
FilatovNikita2019-05-01 22:41:21
Books
FilatovNikita, 2019-05-01 22:41:21

Should I read Tanenbaum's Modern Operating Systems before reading Computer Architecture?

Good afternoon! I have a book by Tanenbaum "Modern operating systems" and is there any point in reading it if you are not deeply versed in computer architecture.
I would like to know the opinion of experienced people, is it worth studying it or is it better to understand architectures first, or maybe even better to read these books at the same time?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
J
Johnny Smith, 2019-05-01
@Olek1

Read those books that you can easily read. And in the order in which you understand everything. If you often start to google while reading, then it is better to switch to another book, and later return to the first.
If everyone recommends you a particular book, but even understanding what it is about, you read it hard and get tired, then drop it and look for another one that you read for pleasure, and not through force. Someone can read one book easily, and someone else can shit with bricks when reading, and vice versa. All books and people are different. How many people, so many opinions and views from different angles. You are no longer at a school desk, where you generally have no choice in the books on which to study, learn to make it fun, and not stepping over yourself. Combine useful with pleasant.
Try at least one of them to start reading, if it doesn't work, start another. If both do not enter, then the third, there are millions of books. Until you find yours. Only trial and error will help you find the books tailored for you.

V
Victor Bomberow, 2019-05-02
@majstar_Zubr

If you are not interested in Computer Architecture, then you should not, because the book is very serious and everything is explained there just galloping across Europe on horseback. What is covered in a book in one chapter, I went through hours of disciplines in total for about a year of full-time education.
I really didn’t like the way the material was presented, it seemed to me that the book was written simply as a summary, because the material is really big, what you know is easy to remember, and new information is hard to give.
I advise you to read and understand the chapters about processors, but in general, you can read this book just for familiarization and broadening your horizons.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question