Now that I've finished this week's class lessons, this is what I've learned:

1. The homework the professor tasked us to do last week ended up having all of my classmates being unable to finish it, let alone program it; the task is super difficult.
2. He mentioned that in another class, he gave them the same homework, and gotten to know that there's one student said he was able to complete it. However, the student didn't demoed (or showed) his program, so the professor extended the period of this homework to be dued some time later in order for both classes to "iron this assignment out".

He didn't spoke of the given assignment any hints or anything, and told us to "think" about it. He wanted us to do more than just reading books and passing the class, thus began the reign of his "experimentially education"... Something I didn't get the picture quite well. He said to us that the academy has two different types of educational purposes: "educational" and "research". The former is about how the academy teach the students concepts, theory, algorithms, etc. The latter is about how the academy lets the students "do" those concepts, theory, etc., and letting them do some researching. And all of this have to do with why he would task us to do this assignment.

In short, I now have a exaggeratedly good reason for me to program on a Sunday weekend with a bad mood. Thanks for some tips, and I'll seek to it with my Google skills.

Seconding the forkbomb. I wrote up a very simple forkbomb just now that completely locked up the computer in less than five minutes. Only took 5 lines of code. It didn't suck up all the CPU, but it sure ate up the RAM quick enough...

[color=#1C2837][size=2]"and then try multithreading to achieve a busy 100% stable CPU"
[color="#1c2837"][size=2]

[color="#1c2837"][size=2]less threadlike would have more busier CPU.